When the target market is Portugal, choose rotating residential (per GB) or static residential (per IP/month) by task. pt-PT/EUR/código postal 4+3 checks plus Portugal ecommerce and localization pointers link to on-site scenes; inventory follows the console; prices follow the console. Iberia primary contrast vs Spain (PT ≠ ES clone); secondary vs Brazil and FR/IT/DE/NL (PT ≠ BR; EUR ≠ BRL; pt-PT ≠ pt-BR).
What this Portugal page solves
Once the target market is Portugal, the next step is usually not another product brochure—it is two decisions:
- Pick product class by task: public-side sampling / monitoring / localization, or authorized store long-lived identity
- Confirm in the console that Portugal exits are orderable (cities and stock always follow the backend)
This is the Portugal country landing under Locations: map “Portugal × rotating/static” to on-site products and scenes—not a city inventory table. Still need the class frame? Rotating vs static residential. First-time buyer overview: How to choose a residential proxy. Sister markets: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland. Hub: Locations. Localization / public-path self-check deep-read: Localization testing. Store map: Ecommerce.
When you also run Iberian exits in parallel, open the Spain sister (primary contrast ES); Portuguese-language-family but different-market secondary via Brazil; EU ecommerce-hub secondary via France, Italy, Germany, and Netherlands. Mainland China is out of scope for use on this site—we do not promise CN nodes. This Portugal page is not a Spain, Brazil, France, Italy, Germany, or Netherlands clone—do not paste those bodies here, even when PT is discussed alongside ES or BR or FR/IT/DE/NL (PT ≠ ES / PT ≠ BR). This page covers Portugal exits only—do not treat Spanish, Brazilian, French, Italian, German, or Dutch storefront/localization as this Portugal proxy page.
Lawful, authorized commercial and technical use only. Portugal / Iberia scenes mean authorized business and self-checks on publicly reachable paths—not unauthorized access or bypassing platform rules. Mentions of Worten, Fnac.pt, or CTT (Correios de Portugal) are limited to authorized store operations and public-path localization / assortment / tracking self-checks (optional Continente / OLX.pt as secondary localization examples). Mentions of tax display are localization notes only (e.g. how IVA / VAT-PT fees may appear; Portugal is in the EU VAT area)—not tax advice; do not invent product VAT claims. Not supported for use in mainland China.
How to split Portugal market: rotating by GB vs static by IP
Rotating residential (per GB)
Fit when you need rotatable, Portugal-selectable, usage-flexible exits: public data sampling, price monitoring, ad creative / landing self-checks, pt-PT European Portuguese copy / EUR pricing / código postal 4+3 delivery options short-flow previews (optional en-PT English ecommerce UI note—pt-PT ≠ pt-BR), public-path UI spot checks, and Portugal ecommerce-context public-side assortment and competitor-page checks within an Iberian frame, etc. Entry: Rotating.
Billing per GB: about $0.40/GB; 100 TB full bundle about $0.20/GB (full bundle only; not split; 1 TB = 1,000 GB). Math: Billing GB vs IP. Console wins on price.
One short flow (finish checkout or a settings page once—e.g. verify a EUR price and a city/region 4+3 postcode delivery option) can use a sticky session—same exit briefly; sticky ≠ monthly static. Params: console. Detail: Sticky vs static. Multi-page / multi-sample → rotate; do not leave sticky always on.
Static residential (per IP / month)
Fit when you need a relatively fixed exit for the term: authorized Portugal-market store backends (often discussed alongside Spain static setups in an Iberian context, Brazil static setups in a Portuguese-language-family context, or France / Italy / Germany / Netherlands static setups in an EU ecommerce-hub context, but this page covers Portugal exits only—do not mix ES / BR / FR / IT / DE / NL exits), persistent environments that need consistent network identity. Entry: Static.
Billing per IP / month: shared about $1.50, dedicated about $5 (USD). Boundary: Shared vs dedicated static. Store map: Ecommerce. Console wins on price.
Localization experience self-checks and public-side Portugal / Iberia market research usually do not need monthly static. If the same project has both store backends and public experience / assortment sampling, split configs (static + rotating each on their own path). When Portugal and Spain or Brazil or FR/IT/DE/NL are both in scope, split exits by market as well—do not mix them, do not treat a Portugal exit as a Spain or Brazil or neighbor exit, and do not substitute es-ES, pt-BR, fr-FR, it-IT, de-DE, or nl-NL context for pt-PT (even when Amazon.es / Iberian logistics or Brazilian Portuguese branding appear; and Portugal uses EUR, Brazil uses BRL; even when ES/FR/IT/DE/NL neighbors also use EUR, EUR alone does not make Portugal an ES/FR/DE/NL/IT clone).
One table: Portugal-side task mapping
Choose by task
| Task | Prefer | Why | ZTProxy |
|---|---|---|---|
| Public multi-URL / multi-page sampling, price monitoring, Portugal public research | Rotating + Portugal geo | Traffic + rotatable exits, not monthly identity | Rotating; Price monitoring |
| pt-PT / EUR / código postal 4+3 self-check | Rotating; short sticky for one flow | Public-path regional experience, not store long identity | Localization; Sticky vs static |
| Ad creative / landing self-check | Rotating; short sticky or rotate | Object under check is creative + landing | Ad verification |
| Authorized Portugal store backend; long fixed identity | Static (shared or dedicated) | Relatively fixed exit for the term | Static; Ecommerce; Shared vs dedicated |
| Unsure rotating vs static class / first purchase | Selection guides | Align task and bill unit first | Rotating vs static; How to choose |
Console wins; no platform-review, conversion, inventory, or coverage promises.
Rotating vs static (Portugal context)
| Dimension | Rotating residential | Static residential |
|---|---|---|
| What you buy | Rotatable / Portugal-selectable residential exits + traffic | Relatively fixed Portugal exit for the term |
| Billing | Per GB (~$0.40/GB; bundles on pricing) | Per IP / month (shared ~$1.50; dedicated ~$5) |
| Typical use | Monitoring, ad self-check, pt-PT/EUR/código postal localization spot checks, public-side assortment | Authorized stores, persistent environments |
| Entry | Rotating | Static |
| Common miss | Rotating for long login; sticky as monthly fixed | Static monthly for multi-page public / multi-city delivery sampling |
PT vs ES vs BR (localization axes, qualitative)
| Axis | Portugal (this page) | Spain (contrast) | Brazil (contrast) |
|---|---|---|---|
| UI locale tag | pt-PT | es-ES | pt-BR |
| Currency | EUR | EUR (same currency ≠ same storefront) | BRL |
| Postal form | código postal 4+3 | código postal ES | CEP |
| Authorized public-path examples | Worten / Fnac.pt / CTT | see Spain | see Brazil |
| Takeaway | This page covers PT only | Do not use as PT primary CTA | Do not use as PT primary CTA; language family ≠ market |
How to read Portugal / Iberia scenes (no invented inventory)
Business conversations often mention Portugal ecommerce and localization, an Iberia cluster frame (Portugal often discussed alongside Spain exits, or Brazil exits because of the Portuguese language family; even when Amazon.es / Iberian logistics, Brazilian Portuguese branding, or English UI overlaps, storefront, localization, currency (EUR ≠ BRL), and sovereign market differ), Portugal public-side research, or pt-PT UI display differences. This page’s target market remains Portugal exits:
- Portugal ecommerce / Iberia parallel pointer: authorized Portugal store long identity → static; public assortment, competitor pages, price sampling → rotating. When peers are also in scope, compare Spain first (primary ES); secondary Brazil plus France, Italy, Germany, and Netherlands. Map: Ecommerce. Worten, Fnac.pt, CTT, and similar contexts are authorized-store and public-path localization / assortment / tracking self-checks only (optional Continente / OLX.pt)—not account farming or bypass.
- pt-PT / EUR / código postal 4+3 localization: prefer rotating + Portugal geo; sticky for one short flow (including EUR pricing, 4+3 postcode delivery options, and pt-PT UI; optional en-PT check), rotate for multi-page sampling. Deep-read: Localization. Remember pt-PT ≠ es-ES ≠ pt-BR—Portugal-market UI is framed as pt-PT (do not treat Portugal as Spain or Brazil); for Spain storefront differences, switch to Spain; for Brazil storefront differences, switch to Brazil; for FR/IT/DE/NL storefront differences, switch to those country pages.
- Código postal / city-region delivery self-check: authorized sampling on publicly reachable checkout / shipping / tracking paths only; no promises of carrier outcomes or coverage, and no invented city or postal-code lists. Even when Correos (Spain Post) appears in Spain contexts or CEP appears in Brazil contexts, Portugal paths still follow CTT and Portuguese storefronts—do not conflate Spanish or Brazilian storefront/localization into this page; do not treat Correos or Brazilian mainstream storefronts as Portugal primary CTAs.
- Vs Spain, Brazil, and EU hubs (PT ≠ ES / PT ≠ BR): Portugal, Spain, and Brazil are often paired in Iberian / Portuguese-language-family / EU ecommerce commercial talk, but locale tags differ (pt-PT ≠ es-ES ≠ pt-BR), storefront and localization paths differ, currency differs (EUR ≠ BRL; even when ES/FR/IT/DE/NL also use EUR, EUR alone ≠ ES/FR/DE/NL/IT clone), and sovereign markets differ; this page covers Portugal only—do not conflate Spanish or Brazilian storefront/localization into this page. For Spain exits, switch to Spain; for Brazil exits, switch to Brazil—do not use this Portugal page as ES or BR. Prefer country name + link contrast for sisters rather than littering foreign currency codes in the Portugal body (EUR alone is correct; BRL only when contrasting Brazil).
- Mainland boundary: this site is not supported for use in mainland China; we do not promise CN nodes.
- Portugal ecommerce & localization pointer: a qualitative reminder that public paths may show pt-PT copy, EUR pricing, código postal 4+3 / city-region delivery differences, or checkout fee display differences (including IVA / VAT-PT display—localization note only—not tax advice; Portugal is in the EU VAT area / eurozone); this site does not provide translation services and does not promise that a given language pack “will always appear.”
- Competitor SERP themes (qualitative only): match rotating vs static to the task; verify Portugal exit first, then test locale / currency / delivery; split hybrid setups when one project needs both store login and public sampling; do not treat PT as an ES or BR clone. No invented volumes or rankings.
Locations is the browse entry; whether Portugal is orderable, and city/resource detail, always follow console/backend. This page invents no city counts, coverage %, or availability SLA. Smoke-test with small traffic or a short term before scale.
If the business target is another market instead of Portugal, switch to: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland.
How to read price
- Rotating: about $0.40/GB; 100 TB full bundle about $0.20/GB (not split)
- Static: shared about $1.50 /IP/month; dedicated about $5 /IP/month
- USD list; self-serve may follow reseller settings—console and Pricing win
- Cost frame: Billing GB vs IP
- Payments context: USDT/USDC OK; Visa/Mastercard applying / pending
Pre-order checklist
- Public-side experience / sampling / Portugal market research, or authorized store long identity?
- Target market confirmed Portugal? Console shows matching resources? Split Portugal vs Spain or Brazil or FR/IT/DE/NL configs when both are in scope (PT ≠ ES / PT ≠ BR; pt-PT ≠ es-ES ≠ pt-BR; EUR ≠ BRL; EUR alone ≠ ES/FR/DE/NL/IT clone; do not mix Spanish/Brazilian or neighbor storefronts)?
- Short sticky or rotate? (params: console)
- Bill by GB or IP×month? Open Pricing
- Access: Docs quickstart; protocol list: HTTP / SOCKS5 setup
- Lawful authorized use? Stay outside mainland China use restriction? First purchase: How to choose
FAQ
Should Portugal work buy rotating or static?
Public-side monitoring, ad self-check, pt-PT/EUR/código postal 4+3 localization spot checks, public research → prefer Rotating. Authorized store long identity → prefer Static. Class frame: Rotating vs static.
Who decides Portugal inventory and city coverage?
The backend / console. This page lists no city inventory numbers; the Locations hub is a browse entry only.
How is Portugal rotating residential priced? Which payments?
Per GB, about $0.40/GB (bundles on pricing). USD list; console and Pricing win. Payments context: USDT/USDC OK; Visa/Mastercard applying / pending.
Can a sticky session replace a Portugal static IP?
No. Sticky only tries to keep the same exit for a short window; static is monthly fixed identity. See Sticky vs static.
How to configure pt-PT, EUR, or código postal 4+3 localization?
Prefer rotating + Portugal geo; sticky for one short flow (EUR / 4+3 postcode / pt-PT UI; optional en-PT), rotate for multi-page sampling. Deep-read: Localization. For Spain exits, switch to Spain; for Brazil exits, switch to Brazil; for FR/IT/DE/NL exits, switch to those country pages (PT ≠ ES / PT ≠ BR; pt-PT ≠ es-ES ≠ pt-BR; EUR ≠ BRL; even when Amazon.es / Iberian logistics or Brazilian Portuguese branding or English UI overlaps, storefront and localization differ; even when neighbors share EUR, Portugal is not an ES/FR/DE/NL/IT clone).
How does this differ from US / JP / SG / UK / DE / AU / CA / FR / NL / KR / IT / ES / BR / MX / IN / ID / TW / AE / SA / TH / PH / VN / MY / TR / EG / PL / HK / NZ / IE / AT / BE / CH / SE / DK / NO / FI pages?
Same selection skeleton, different target market; this page emphasizes pt-PT / EUR / código postal 4+3, Portugal ecommerce and localization, Iberia framing, and parallel sisters Spain (primary ES), Brazil, France, Italy, Germany, and Netherlands—and states PT ≠ ES / PT ≠ BR clones (Portugal is not Spain or Brazil; pt-PT ≠ es-ES ≠ pt-BR; EUR ≠ BRL; EUR alone ≠ ES/FR/DE/NL/IT clone). Compare: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland.
What is the use boundary? Account farming or multi-account evasion?
Lawful, authorized commercial and technical use only, plus self-checks on publicly reachable paths. No account farming, multi-account evasion, or rule bypass language; no promises of platform review or conversion outcomes.
Is mainland China supported? Who wins on price?
All proxy products on this site are not supported for use in mainland China. List prices are USD; orders and invoices always follow the console and Pricing.
Next steps
- Use the task table to pick rotating or static
- Open Rotating or Static and confirm Portugal exits in the console
- Check Pricing; access via Docs quickstart
- Scenes: Localization · Ecommerce · Price monitoring · Ad verification
- Other markets: Locations · United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland
- First-purchase overview: How to choose
Need help: [email protected] or on-site support (no invented response SLA).