Start with a closed local profile

Mac Profiles provides cookie import and export for closed local profiles. Keeping the profile closed avoids a race between a website changing cookies and a person importing replacements. The current cookie manager does not expose the same operation for team profiles. Choose the destination carefully and use a small, authorized test set before replacing important state.

JSON can carry richer attributes

The Mac Profiles JSON representation includes cookie attributes such as SameSite alongside the basic name, value, domain and path. JSON files from unrelated tools can use different field names or conventions, so the extension alone is not a compatibility guarantee. Check the import validation result and the values shown by the receiving tool.

Netscape format has a narrower shape

The longstanding Netscape cookie-file format uses a tab-separated record. Curl documents this format and its conventions. It cannot represent every modern cookie attribute that a richer JSON record may contain. Mac Profiles makes that format loss explicit when an export would discard attributes; choosing a familiar file format should not hide the loss.

Cookies are only one part of site state

Neither export recreates localStorage, IndexedDB, open tabs or arbitrary in-memory application state. A website can also expire or revoke a server-side session independently of the file. A syntactically valid import therefore cannot guarantee that a service accepts the restored login. Cookie values can contain sensitive session material, so transfer only the intended entries to the intended recipient.

Verify the result through a restart

After importing into a test profile, reopen it and visit the relevant site. Close the profile normally, wait for saving to finish, then reopen it again. Check the behavior you need rather than relying only on the number of imported records. Keep the source file until that validation succeeds, and remove unnecessary copies according to your team's handling policy.