Moving from Camino

Keep a backup of your Camino data before your first visit.

Automatic import

When the Macino profile folder does not exist, Macino checks ~/Library/Application Support/Camino for a profile containing prefs.js. It prepares a copy in ~/Library/Application Support/Macino, leaving the original intact. Later launches use the Macino copy.

An existing Macino folder—even an empty one—prevents automatic import. A custom profile path does too. The importer does not merge an old profile into an existing Macino one.

What comes across

Supported bookmarks, search engines, preferences, history, permissions, unexpired cookies, password-saving exclusions and optional ad-blocking CSS can transfer. Existing Macino settings and matching cookies take precedence.

What stays behind

Camino’s saved passwords live in the macOS Keychain, outside the profile folder. Old Gecko certificate databases, form history, local storage, plug-ins, session state and caches are not imported. Certificate exceptions need to be granted again.

If import did not happen

Quit Macino and keep copies of both profile folders. You can import bookmarks separately through File → Import Bookmarks…. For a full manual retry, ask through the project support route before moving or deleting any profile files.

Custom profiles share preferences and WebKit website data; they are not isolated browsing identities. See Recovering saved data.