After converting a proxy format: where to paste it in AdsPower

Where should the converted result go?

Once you have authorized proxy details, inspect the client’s requirements for Proxy Host, port, username, password, or Proxy URL rather than pasting into the first box. One box may accept a URI or recognize four-part autofill; box count alone cannot determine format.

This guide uses AdsPower’s official fields to answer how to configure after conversion. Chinese help was last modified October 14, 2025 and English help August 26, 2025; these are existing instructions, not a new feature announced today. Other clients, versions, and QR imports require their own docs.

Step 1: confirm the actual protocol before formatting

Confirm host, port, authentication method, and the node’s actual protocols from delivery details. Choose HTTP, HTTPS, or the interface’s “Socks 5” accordingly. Do not invent a prefix or port to make text fit; conversion does not add protocol support to the node.

Use https://puppyip.com/tools/proxy-converter when formatting is needed. It works locally in the browser without login and offers six text outputs; TXT/CSV files are limited to 1 MiB and batches to 100 entries. This guide uses the output matching your client rather than covering bulk rules. It neither uploads nor saves input, nor validates passwords, connectivity, or exits.

If the client explicitly accepts four parts, choose IP:port:username:password. For authentication-first notation choose username:password@IP:port. Select a complete URL only when the client requires it and supports that protocol. See the proxy format/URI guide in Sources for special characters and bulk rules.

Step 2: where AdsPower accepts four-part autofill

This fictional documentation example uses host 192.0.2.10, port 3128, username demo_user, and password demo_pass. 192.0.2.10 is reserved for documentation; credentials are invented, not a working line. No connection test was performed with it.

The four-part form is 192.0.2.10:3128:demo_user:demo_pass. AdsPower’s Chinese help says proxy host:port:account:password can autofill from Proxy Host. After pasting, check each field: 192.0.2.10, 3128, demo_user, demo_pass. The absence of an input error is not sufficient.

The same example can be demo_user:[email protected]:3128. Chinese help says account:password@host:port can be copied separately into corresponding fields. Do not assume host-field autofill for it, or put the whole string in a separate password box.

Step 3: check individual fields against the English interface

English help uses + New Profile → Proxy, selects the actual proxy type, fills Host:Port, Proxy username, and Proxy Password, then Check Proxy. For the fictional example, Host:Port is 192.0.2.10:3128, username demo_user, password demo_pass. Follow the current interface’s field labels and prompts.

Chinese autofill and English individual fields both require host, port, and authentication in their proper places. The English page does not guarantee every representation imports. If your labels or layout differ, consult that version’s help rather than repeatedly guessing with real credentials.

Step 4: do not mix raw passwords and URI encoding

Separate authentication fields take the delivered raw username/password. In a full URI, encode credentials according to URI/client rules: a password’s @ may become %40 inside URI credentials, but that does not mean entering %40 in the password field. Do not arbitrarily decode a raw password that already contains a percent sign.

Do not encode the entire address, double-encode, or delete password punctuation/spaces to pass a format check. If credentials conflict with four-part separators, verify original values and client support, then choose unambiguous fields using the format/URI guide. This article has not verified every AdsPower special-character, IPv6, or QR import case.

Step 5: after a passed check, open the actual browser

Click Check Proxy or the current connection test. English help says passing means AdsPower can connect to the proxy, then OK creates the profile. Chinese help also requires opening the browser to confirm actual effect and webpage access. A connection result is not acceptance of every app, website, or account permission.

In your authorized browser environment, use a permitted neutral target to confirm the exit and continue checking the network path as needed. Repeated important-account logins do not replace basic checks. Converter text, server-side detection, or one successful request is not full profile acceptance. See the pre-purchase acceptance checklist in Sources.

If checking fails, compare protocol, host, port, and raw credentials, noting the message and step. If fields are correct, use the connection troubleshooting checklist. One failure does not establish an unusable proxy; changing format cannot be guaranteed to fix it.

Step 6: keep records and fixed conditions while diagnosing

Record account purpose, tool/version, profile name, actual protocol, format, expected region, responsible person, and exit-verification time. Do not put credentials or complete addresses in public screenshots or ordinary shared documents; redact to the fields needed for diagnosis.

For a long-used authorized account, traceable configuration/exit conditions help compare outcomes. Review records when problems occur, changing one confirmed faulty setting at a time rather than format, network, and exit together. A fixed exit is a configuration/acceptance goal, not a guarantee of permanent stability or account safety.

Region databases can disagree. Record source, time, and observation and cross-check; choosing a more favorable lookup does not establish compliance. Proxy region is not platform account eligibility: platform rules, account state, and authorization still need separate checks.

Prepare before a short test; share credentials only where needed

For PuppyIP’s free test, read the claim guide and prepare client/fields before confirming. Successful confirmation starts 15 minutes; login, personal eligibility, and regional resources constrain claiming. A login-free converter does not mean login-free resource claims or guaranteed inventory.

PuppyIP serves compliant overseas businesses and authorized personnel. It is not offered in mainland China, and use within mainland China is prohibited; an offshore IP does not change service scope. A format guide, connection check, or exit cannot replace service/account eligibility.

Local processing applies only to the converter. After copying to AdsPower, another client, clipboard, or file, users safeguard credentials under those tools’ mechanisms; actual connection checks make network requests. Never post real addresses publicly, send them to unfamiliar online converters, or include them in unrelated tickets.