Profile templates

A template keeps the settings of a new profile under a name, and the Templates window holds them all. The way there: Profiles, the arrow to the right of New profile, then Manage templates…; the batch and import windows have a Templates button too. A template copies your decisions, not the fingerprint.

What a template holds

A template has the fields of the New profile window and a block For every new profile with three more: a status, extensions and a profile password.

Field	What a new profile gets
Fingerprint template	The system sites see; the fingerprint itself is new for each profile
Scenario and Group	As in the template; a group open in the list wins over the template group
Proxy	One for all, a different one from the list for each, or a random one from the list
Notes and Tags	Copied into the profile, up to 12 tags
Status	One of your statuses
Extensions in every new profile	The extensions you ticked, from the Extensions section
Profile password	Asked before the profile opens
The rest	Opening address, Browser kernel, Run without a window (for automation), Location, Traffic saver, Port scan protection, WebRTC mode, Launch arguments and the IP change of the proxy

Make a template

1
From a profile
Open a profile, set it up, press Save as a template at the bottom of the window and type a name. The template takes the fields of that window.
2
From scratch
In the Templates window press New template. The profile window opens as a template, and its first field is Template name.
3
Save
Press Save the template. Its row in the list shows the system, the proxies, the extensions, the tags and the status.

Proxies for many profiles

The Proxy choice has three options. One proxy for every profile sends them all out through one address, and the window warns that a site can link two of them.

A different one from this list for each profile gives a new profile a proxy that no profile uses yet; a profile in the recycle bin keeps its proxy taken, since it comes back with it. When all are taken, the app says so before anything is made. A new template starts with this option.

A random one from the whole list suits proxies that change the address on their own: two profiles can get the same one.

Tick proxies from the library or type them into Add proxies as lines; lines go into the library and into this list. Profiles made at the same moment by a batch, a quick profile and the local API still get different proxies.

Status, extensions and a password

The status is set when the profile is made, and the extensions go on right after it. If an extension did not go on all of them, the app names it, and the profiles stay.

A profile password needs an account: without signing in, the app does not save it into a template, and a template with a password makes no profile until you sign in. The password reaches the server in the same step that makes the profile, and the window shows only that a password is set.

The default template

Use for new profiles makes a template the default one, with the Default badge on its row. One template is the default at a time; Stop using for new profiles takes the mark off.

The default template fills the New profile window. In the quick profile menu the four systems come first, and below them, under Templates, it is the first one: Default: name. It is picked in a batch and in For every row of an import, and fills a profile made over the local API or MCP when the request names no template.

Change, copy and delete

Edit opens the template in the profile window. Changes apply to profiles created after them.

Duplicate makes a copy with the word copy after the name, and the copy is not the default. Delete asks first and removes the template alone; the profiles made from it stay.

Templates over the local API and via MCP

GET /api/v1/preset/list gives the templates of this computer: presetId, name, system, whether it is the default, the proxy option and the number of proxies, the status, the number of extensions and whether it sets a password. Proxies and the password are not in the answer.

POST /api/v1/profile/create without presetId takes the default template, and the body wins over it; presetId none makes a profile without a template. The MCP tool create_profile takes presetId the same way.

Request: POST /api/v1/profile/create { name: Shop 7, presetId: none }
Answer, for example: { code: 0, data: { profileId, profile, presetId: null } }
No free proxy: { code: -1, msg: preset_no_free_proxy, data: { message, free: 0 } }
A bad presetId: presetId: 5 gives { code: -1, msg: bad_param, data: { param: presetId, message } }

A template that cannot be used answers a code that starts with preset_, for example preset_not_found or preset_no_free_proxy, and nothing is made.

What this does not do

It does not copy the fingerprint, cookies or site data: a profile from a template starts as a new machine.
It does not change profiles already made.
It does not leave this computer: the team does not see your templates, and the dashboard on the site does not offer them.
It does not keep more than 100 templates, and a name is up to 60 characters.

Where this is decided

The stands below run the real app in a hidden window instead of reading a file.

The Templates window and its buttons; the default template in the New profile window, a quick profile, a batch, an import and the local API; a free proxy for each, a profile in the recycle bin keeping its proxy, a refusal before anything is made; status and extensions on each new profile; separate machines: apps/desktop/test/заготовки-окно.js
The profile password from a template is on the server from the first moment; without an account a template with a password makes nothing: apps/desktop/test/заготовка-пароль-статус-живьём.js
Profiles made at the same moment by a batch, a quick profile, the local API and the New profile window get different proxies: apps/desktop/test/заготовка-раздача-разом-живьём.js
MCP create_profile with no presetId, with presetId none and with another template; a bad presetId refused in words: apps/desktop/test/заготовка-api-и-mcp-живьём.js
A template from a shared profile does not carry the owner's proxy password for a team member or an operator: apps/desktop/test/пароль-чужого-прокси-строгое-правило-живьём.js

Questions

What happens when the list has no free proxy?: Nothing is made. The app says how many free proxies the template has and how many profiles were asked: add proxies to the template or create fewer.
Does a change to a template reach profiles I already made?: No. Changes apply to profiles created after them, and profiles made from the template earlier stay as they are.
A template saved from a profile shared with me has no proxy password. Why?: The password of that proxy belongs to the profile owner. Team members and operators do not get it, and others get it only with full access to the profile, so it does not go into a template.

Next to this

Make your first template

The free plan gives two profiles, with no time limit and no card.

Sign-ups paused for now Knowledge base