> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/getting-started/setting-up-your-proxidize-proxies.md).
# Setting Up Your Proxidize Proxies
How to find your proxy credentials and connect Proxidize proxies on desktop and in automation tools.
Once you have an active plan, connecting your proxies takes just a few minutes. This guide shows you where to find your credentials and connect them on desktop or in automation tools.
{% stepper %}
{% step %}
## Find your proxies and copy your credentials
All of your proxies *( Mobile, Residential, and Proxy Builder (Legacy) )* live in one place: your dashboard at [app.proxidize.com](https://app.proxidize.com). Open the product you purchased to see its proxies.
Getting your proxy takes just a click. The exact spot depends on your plan. Either way, proxies are copied in one of two formats:
* `IP:Port:Username:Password`
* `Username:Password@IP:Port`
**On the Per Proxy plan:** next to each proxy you'll see a copy button for each protocol, **HTTP** and **SOCKS5**. Press the copy button for the protocol you want, and the full proxy is copied to your clipboard in your chosen format. No manual assembly needed.
{% hint style="info" %}
Credentials are generated automatically and don't change when your IP rotates, so you never need to update your tools after a rotation.
{% endhint %}
**On Per GB plans:** all of your proxies are listed together under the **Formatted Proxy List** section of the dashboard. Open it to see every proxy in one place, pick your protocol and format, and copy them individually or export them in bulk.
***
**Authentication options:**
* **Username / password:** the default. Works in any proxy-compatible tool.
* **IP Whitelist:** authenticate by your public IP instead of a username and password. Best for servers and automation. If your public IP changes, add the new one to your allowlist or access will stop.
{% endstep %}
{% step %}
## Choose how to connect
The best connection method depends on your device.
{% hint style="warning" %}
Proxy traffic can only reach destination ports `80` and `443`.
{% endhint %}
#### 1. On a desktop (PC or Mac)
We recommend the Proxidize Proxy Extension:
**Recommended:** [**Proxidize Proxy Extension**](/proxidize-proxies/proxidize-proxy-extension.md)**.** A lightweight browser extension that lets you connect to a proxy in one click, switch between proxies, and test them, without changing your system settings. Best for quick setups and testing.
* [Proxidize Proxy Extension for Chrome](https://chromewebstore.google.com/detail/proxidize-proxy-extension/gccdbcipcjgfnjlegofdhflkifgkdmpb)
* [Proxidize Proxy Extension for Firefox](https://addons.mozilla.org/en-US/firefox/addon/proxidize-proxy-extension/)
#### 2. In scripts and automation tools
Proxidize proxies work with any proxy-compatible tool. Use the format most tools expect:
```
http://username:password@hostname:port
```
The exact input format varies by tool, check that tool's own documentation.
#### 3. Last option: an anti-detect browser
If the extension doesn't fit your setup, for example because you need several separate browser profiles, you can use an anti-detect browser instead. Add your Proxidize credentials to each profile's proxy settings.
{% endstep %}
{% step %}
## Test your connection
Before running a full workflow, confirm the proxy works. You can:
* Use the **Proxidize Proxy Extension** to connect and view the egress IP, or
* Run a quick command-line check:
```
curl -x http://username:password@hostname:port https://api.ipify.org
```
If the returned IP is different than your local IP, you're connected.
{% endstep %}
{% endstepper %}
***
### Troubleshooting
If a proxy won't connect, first re-check the username, password, protocol, and port. Then rotate the proxy (Per Proxy) or switch the session key or Access Point (Per GB), and test again with a curl request to isolate whether the issue is the tool or the proxy.
If your target uses a port other than `80` or `443`, the proxy cannot reach it.
For more help, reach the team via live chat at [app.proxidize.com](https://app.proxidize.com) or email .
### Related
* [Quick Start with Proxidize Proxies](/getting-started/quick-start-with-proxidize-proxies.md)
* [Choose Between Mobile and Residential Proxies](/getting-started/choose-between-mobile-and-residential-proxies.md)
* [Verification](/account-and-billing/verification.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.proxidize.com/getting-started/setting-up-your-proxidize-proxies.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
