Add, import, and assign proxies

A proxy defines the network exit used by a browser profile. We recommend saving and checking a node on the Proxies page before assigning it. You can also quick-add a standard proxy while creating a profile and use it immediately.

Choose an add method

Scenario	Where to start	Suitable input
Add one standard node	Proxies → Add proxy → Standard proxy	HTTP, HTTPS, or SOCKS5
Add several standard nodes	Proxies → Bulk import	One address per line
Use a node while creating a profile	Profile settings → Network connection → Use proxy → Quick add proxy	One standard node
Import a JSON or YAML proxy configuration	Proxies → Add proxy → Advanced proxy	One node or a configuration containing several nodes

See the “Advanced proxies and multi-hop routes” guide for advanced configurations and multi-hop connections.

Add one standard proxy

1. Open Proxies and select “Add proxy.”
2. Select “Standard proxy.”
3. Choose HTTP, HTTPS, or SOCKS5.
4. Enter the server address and a port from 1 to 65535.
5. Enter a username and password only if the provider requires authentication.
6. Optionally choose a group and record the region, provider, expiry date, or a note.
7. Save the proxy and select “Check connection” on its row.

Enter only a hostname or IP address in the server field. Do not repeat the protocol or port there. Leave both credential fields empty for a proxy that does not use authentication.

Quick-add and assign a proxy

On the create or edit profile page, select “Use proxy,” then select “Quick add proxy.” You can paste any of these formats:

http://user:password@host:port
https://user:password@host:port
socks5://user:password@host:port
host:port
host:port:user:password

Select “Recognize,” verify the protocol, address, port, and credentials, and then select “Add and use.” The proxy is created and selected automatically.

Quick add supports standard proxies only. You can manage its group, provider, expiry date, or upstream proxy later on the Proxies page. If you need an advanced protocol or configuration, import a separate advanced proxy from the Proxies page; a standard proxy cannot be converted into an advanced proxy.

Bulk import standard proxies

1. Open Proxies and choose the destination group first. If no group is selected, the nodes are saved as ungrouped.
2. Select “Bulk import.”
3. Enter one proxy per line in any of these formats:

host:port
host:port:user:password
http://host:port
https://user:password@host:port
socks5://user:password@host:port

4. Check the number of recognized lines shown by the page, then start the import.
5. If only some entries fail, check the successfully imported nodes first and then review the protocol, port, and credential format on each failed line.

The host:port and host:port:user:password formats are imported as HTTP when they do not include a scheme. Use a complete URL with the corresponding scheme for HTTPS or SOCKS5 nodes. The recognized count is a format preview, not complete validation of the protocol, address, and port. Make sure every line has an explicit address and a port from 1 to 65535. After import, verify each protocol, address, and port and run a connection check.

Blank lines and lines beginning with # are ignored. If a username or password contains URL-reserved characters such as @, :, or /, prefer the complete URL supplied by the provider or URL-encode those characters first.

Assign a proxy to a browser profile

1. Create or edit a profile and find “Network connection.”
2. Select “Use proxy.”
3. Select “Choose proxy,” then search by address, region, note, or group.
4. Select a node and save the profile.

Each profile is assigned one entry proxy. If that entry has an upstream proxy, the complete route is used automatically at launch. A node or route already occupied by another profile is not offered for duplicate use.

To remove the proxy, switch to “Direct connection” and save. To change the proxy, close the running profile first, update the selection, and launch it again so the exit does not change inside an active browsing session.

Check before launch

• Run “Check connection” at least once.
• For a multi-hop route, also run “Check full connection.”
• Confirm that the displayed exit location matches your expectation.
• Do not treat one high-latency result as proof that a node is dead. Retest later or from another local network.

Results come from the current device and describe the network at the time of the check. Changes to the proxy service, local network, firewall, VPN, or DNS can still affect a later launch.