When you buy an account, the listing states a delivery format: login:pass, cookies or IAM. The choice decides how quickly and how frictionlessly the account spins up in your environment. One format is ideal for manual login, another for antidetect, a third for specific software. Let's break down the three main formats, their upsides and what each suits, so you don't wrestle with incompatibility after paying.
login:pass — the base format
It's simply a login and password, sometimes with an email and email password. The most universal and clear option: it fits manual login and most scenarios. The downside is that on first login you type the data anew, meaning you create a fresh session the platform sees as an unfamiliar entry. So with login:pass the right environment and a smooth start matter especially. The format shines when you need full access to the account and email and are ready to log in carefully yourself.
When to take login:pass
- Manual work with one or two accounts;
- you need full control, including changing the data to your own after purchase;
- you take accounts with email to have recovery access.
cookies — a ready session
Cookies are a saved session file (usually JSON or Netscape). Import it into a browser or antidetect and you land in the feed with no password entry. The main upside: you don't create a new login by hand but continue an existing session, which is gentler for the account at the start. That's why cookies are a convenient format for antidetect: the session imports into a profile in a couple of clicks. The downside is that cookies have a shelf life and require the environment (proxy geo, fingerprint) to match where the session was created.
When to take cookies
- Work through an antidetect browser with profile import;
- you want a gentle login with no manual entry at the start;
- it matters to deploy many profiles fast.
IAM — a format for automation
IAM (Instagram Account Manager / an auth string) is a compact format where the account data is packed into a single string for import into specialized software and account managers. Its strength is scale: strings load conveniently in batches, the software parses the fields itself and spreads accounts across profiles. The downside is that the format is tailored to specific tools, and for manual work it's overkill. IAM is taken by those working through software managers and operating accounts by volume, not one by one.
Comparison table
| Format | What it is | Better for | Caveat |
|---|---|---|---|
| login:pass | Login, password, often email | Manual login, full access | First login = a new session |
| cookies | A ready session file | Antidetect, gentle start | Has a shelf life, needs geo match |
| IAM | A string for a software manager | Mass automation | Tailored to specific software |
How to choose for your software
Start from the tool, not the other way around. Working by hand through an antidetect, take cookies (plus login:pass in the package as a recovery backup). Running mass tasks through an account manager, check which format it accepts and take IAM if the software is built for it. Need full owner access including email, login:pass is a must. It's ideal when the seller hands over a combination: cookies for a fast login and login:pass with email just in case.
How the formats relate to each other
The formats aren't mutually exclusive but layers of the same access. login:pass is the root: with a login, password and email you own the account fully and can log in again if the session expires. cookies are a handy shortcut to an already-open door: fast, but they go stale over time. IAM is the same bundle packed for a software pipeline. The practical takeaway: cookies save time at the start, but it's login:pass with email that's your insurance, so buy accounts where the base access comes together with the session. Then when cookies expire you don't lose the account, you simply log in again and refresh the session if you want.
Mini-FAQ
Which is better for antidetect, cookies or login:pass?
Cookies: importing the session into a profile gives a gentle login with no manual entry. Keep login:pass alongside as a recovery reserve.
Why does it ask for a code after importing cookies?
Usually the cookies are stale or the proxy geo doesn't match where the session was created. Check the IP region; if needed use login:pass or request a replacement.
Is IAM suitable for manual work?
Overkill. IAM is built for software managers and scale; for one or two accounts login:pass or cookies is simpler.
Conclusion
login:pass is universal full access, cookies is a gentle login for antidetect, IAM is a format for mass software. Choose by the tool and keep login:pass with email as insurance. At Instara accounts are delivered in login:pass, cookies and IAM formats, including antidetect-ready and with email: auto-delivery 24/7, payment via USDT (TRC-20)/SBP, invalid replacement. Questions: @instaraallert_bot.