Import and export

Streams a zip. Refused while the profile is running, because a live browser has databases open and partly unflushed and the archive would capture a torn session. Cookies survive the round trip because profiles are encrypted with a fixed key rather than one bound to this machine’s keychain.

One archive containing several profiles.

Send the zip bytes as the raw request body. A Mosaic export is imported verbatim — profiles keep their identities and cookies, and one whose id already exists is skipped rather than overwritten. An export from GoLogin, Dolphin Anty, AdsPower, Octo Browser or Multilogin is recognised from the shape of its contents, never its file name, and mapped across: name, notes, proxy, start pages, cookies where present, and whichever of platform, User-Agent, timezone, language, screen, cores and memory that product recorded. Anything it did not record is generated coherently rather than filled with a constant, and the vendor name is added as a tag so provenance survives. The response carries a source object naming the vendor and what could not be carried across. A file matching no known product is imported only on the fields every product shares.

An archive made on a different desktop platform is imported rather than refused — a library exported from a Windows machine and opened on a Mac arrives in full — and every profile that claims a platform this computer cannot be comes back in warned, by name. Those are real profiles in the library, and they will read as masked on a consistency scanner until they are repaired: the fonts installed, their metrics and how the platform rasterises them come from the real machine and no switch reaches them. POST /profiles/bulk/repair-hardware redraws each one from its own seed, keeping the cookies, the canvas identity and the locale. Authoring such a profile is still a 400 — preserving an existing library and typing os: "windows" into a create call are different acts.