Two shapes, one format
A JSON file holds Profiles, proxies, and — if you choose — cookies, in one file. Two CSV files, one for Profiles and one for proxies, are for building or editing rows in a spreadsheet. CSV files never contain cookies.
Feature · Bulk import and export
Agilelogin reads and writes Profiles and proxies as files: CSV for editing in a spreadsheet, or a single JSON file that can also carry cookies. Every import shows what will happen to each row before anything is saved.
Import reads a CSV or JSON file, checks every row, and shows a preview: the Profiles and proxies it will create, rows imported before that it will skip, groups it will create, and rows with a problem in a named field. Nothing is saved until you confirm, and if a row you kept has a problem, nothing is saved at all. Export writes the Profiles you choose and the proxies they use to a file — and proxy passwords or cookies only if you tick them.
One format of Agilelogin's own, in two shapes.
A JSON file holds Profiles, proxies, and — if you choose — cookies, in one file. Two CSV files, one for Profiles and one for proxies, are for building or editing rows in a spreadsheet. CSV files never contain cookies.
The preview lists every row's action and any problem by field. Untick the rows you don't want, or fix the file and preview again. If the file would go over your plan's Profile limit, the preview says so and you choose which rows to keep — nothing is cut off silently.
Everything you import belongs to the account you're signed in with. Groups are matched by name in that account, and a group that doesn't exist yet is created.
One import can hold up to 5,000 Profiles and 5,000 proxies. How many Profiles you can keep still follows your plan's limit.
An export file is a copy you hold; what it contains depends on what you tick.
| Subject | Agilelogin boundary | Operator action |
|---|---|---|
| Proxy passwords and cookies in an export | Left out unless you tick them; when included, written to the file in plain text | Keep the file where only you can reach it — anyone who gets it can use them. Folders synced to the cloud, such as OneDrive Desktop and Documents, upload it automatically. |
| Rows imported before | Recognized and skipped by default, or imported again as new Profiles if you choose | Check the preview's actions before you confirm. |
| Extensions, bookmarks, and other browser data | Not part of import or export | Install extensions again and move other data separately. |
The same steps whether the file came from a spreadsheet or another Agilelogin computer.
Download the CSV template from the import dialog, or export from another Agilelogin installation. Leave the fingerprint column empty and the default template fills it in.
Check each row's action, untick the rows you don't want, and fix any row that has a problem.
The rows you kept are saved together. If the JSON file has cookies, they are written next, Profile by Profile, and any Profile that didn't get its cookies can be retried.
Imported Profiles stay on this computer until you run Sync now in Settings, which uploads them to your account.
What bulk import and export do not do yet.
Not by importing that tool's own file. You can export a spreadsheet there, rename its columns to match Agilelogin's CSV template, and import it. Leave fingerprints empty so the default template fills them in.
Only if you tick them. The file then contains them in plain text and anyone who gets it can use them, so keep it where only you can reach it — folders synced to the cloud, such as OneDrive Desktop and Documents, upload it automatically.
No. Import only writes to this computer. Run Sync now in Settings to upload the new Profiles to your account.
Read how Profiles keep their state and network settings, then start from the CSV template in the app.