Proxy Formats and Exports
The two proxy string formats the generator can produce, what each one looks like, and what the CSV and TXT exports contain.
Last updated
The generator can write an endpoint in two ways, and can export the whole set to a file. Getting the format right saves you from editing strings by hand in a config file.
The Proxy format field
| Format | Template | Example shape |
|---|---|---|
| Host:Port | {host}:{port}:{username}:{password} | proxy.lightningbytes.com:1080:customer-USERNAME:PASSWORD |
| URL | {protocol}://{username}:{password}@{host}:{port} | http://customer-USERNAME:PASSWORD@proxy.lightningbytes.com:1080 |
The dropdown shows each option's label alongside its template, so you can see exactly what will be written before you copy it.
Which to choose
Host:Port is the four-field layout that many tools and dashboards expect when they ask for host, port, username and password separately, and it is usually accepted when pasted into tools that parse a colon-separated list.
URL is the standard connection-string form. Many command-line tools take it directly with a proxy flag, and it is the easier one to read when debugging.
If your tool asks for separate fields, either format gives you the parts, because the table view always splits the endpoint into its four columns regardless of the copy format you chose.
Exports
The Export action offers two file types. Both contain the currently generated set, written in the Proxy format you have selected.
| Export | Contents |
|---|---|
| CSV | A spreadsheet-style file with a header row and one row per endpoint |
| TXT | One endpoint per line, plain text |
The file is named after the product, so a residential export and a mobile export do not collide in your downloads folder.
What is in the CSV
The CSV has a header row naming the fields, then one row per endpoint. In Host:Port format the fields are the four parts of the endpoint. In URL format the protocol is included as its own column, so the file is self-describing.
What is in the TXT
Plain text, one endpoint per line, nothing else. This is the format to paste into a script, a .env style list, or a tool that accepts a list of proxies one per line.
Practical notes
- Export after you generate, not before. The export reflects the current set, so re-export after regenerating or replacing endpoints.
- Keep exports out of version control. They contain working credentials.
- Rotate rather than edit. If a credential leaks, rotate it from the sub-user rather than editing it in every export you produced.