Account Converter

🍪 Cookies → 📱 Android/UID

All accounts are delivered in a single format login:pass[:email:pass][:2fa]|[JSON cookies]. Here you can convert them into the Android/UID format (mobile session). Paste accounts — one per line. Conversion runs right in your browser — data is never sent anywhere.

1. Paste cookie lines2. Click “Convert”3. Copy Android/UID

🍪 Cookies format (as delivered)

login:pass[:email:pass][:2fa] | [JSON cookies] — one account per line

📱 Android / UID format

login:pass:email:emailpass[:2fa] | User-Agent | device | X-MID;...;Bearer IGT:2:...

⚠️ Cookies have no original device or X-IG-WWW-Claim — so the User-Agent and device-id are generated (deterministically from ds_user_id), and the claim is set to 0 (Instagram issues a fresh one on the first request). The session works, but the device fingerprint is synthetic: when imported into mobile software it is less “natural” than native API/Mob accounts.
📱 Android/UID → 🍪 Cookies

All accounts are delivered in a single format login:pass:…|UA|device|…Bearer IGT:2:…. Here it goes the other way — rebuild the delivered Cookies format from an Android/UID mobile session. Paste accounts — one per line. Conversion runs right in your browser — data is never sent anywhere.

1. Paste Android/UID lines2. Click “Convert”3. Copy Cookies

📱 Android / UID format (mobile session)

login:pass:email:emailpass[:2fa] | User-Agent | device | …Bearer IGT:2:… — one per line

🍪 Cookies format

login:pass[:email:pass][:2fa] | [JSON cookies]

⚠️ The real sessionid (embedded in Bearer IGT:2:), ds_user_id and mid are taken from the mobile session and assembled into the browser cookie format (.instagram.com, path /, secure; httpOnly on sessionid). This set is enough to sign in: sessionid is what authenticates, and Instagram sets csrftoken itself on the first request.
🍪 Cookies → 🌐 Browser JSON (Dolphin/AdsPower)

All accounts are delivered in a single format login:pass[:2fa] | csrftoken=…;sessionid=… (or [JSON cookies]). Here the delivered account is assembled into ready-to-import JSON cookies for an antidetect browser (Dolphin Anty, AdsPower, Cookie-Editor). Paste accounts — one per line. Conversion runs right in your browser — data is never sent anywhere.

1. Paste delivery lines2. Click “Convert”3. Copy JSON cookies

🍪 Delivery format (as received in the order)

Cookies as a csrftoken=…;sessionid=…; string or as a JSON array — one account per line

🌐 JSON cookies (for browser)

Array of .instagram.com cookie objects — paste into the Cookies field of a Dolphin/AdsPower profile

⚠️ This just reformats your own cookies into what an antidetect browser accepts (domain .instagram.com, path /, secure, httpOnly on sessionid/datr/ig_did). Always set a mobile/residential proxy matching the account region for the profile. Important: if the account already asked for phone/selfie verification, or you signed in manually with the password, the session (sessionid) may have been invalidated — then importing cookies will not help and Instagram will ask for the same verification.