Web Unlocker or residential proxies: which fits your job
What each product does, how each is billed, and when to use one, the other, or both together.
By DINPROXY Team · · 5 min read
On this page
Residential proxies and the Web Unlocker both help you collect public web data, but they split the work differently. With a proxy, your own code fetches the page through a residential IP. With the Web Unlocker, you send a URL and get the finished page back.
What residential proxies do
A residential proxy routes your requests through IP addresses of real home connections, so target sites see ordinary visitors. Your scraper, browser or HTTP client stays in charge: it sends each request, receives the site's response and decides what to do next.
DINPROXY residential proxies give you:
- Rotation by default, with a new IP for every request, or sticky sessions that keep one IP for up to 120 minutes.
- Location targeting by country, state and city, across 195+ countries.
- HTTP, HTTPS and SOCKS5 on
proxy.dinproxy.com:7777. Usehttp://for HTTP and HTTPS sites andsocks5h://for SOCKS5. - Sign-in with a proxy user, or from a whitelisted server IP without a password.
For HTTPS sites, your client opens an encrypted tunnel through the proxy, so DINPROXY never sees the page contents. Proxies are the natural fit when you control the whole visit: logins, cookies, forms and anything your own browser automation does.
What the Web Unlocker does
The Web Unlocker works one level up. You send a target URL, and it fetches the page, renders JavaScript, retries and works around anti-bot checks, then returns the result. You don't run proxies, browsers or CAPTCHA handling yourself.
- Output: the page's HTML, a PNG screenshot, or both in one request.
- Options: a country to fetch from, waiting for a CSS selector or extra time, custom headers and cookies, and more.
- Four ways to connect: a JSON API, a proxy mode at
unblocker.dinproxy.com:7780for scrapers that expect a proxy, an MCP server for AI assistants, and a command-line tool for lists of URLs.
Because rendering and retries happen inside the request, one request can take up to 2 minutes. Set your client's timeout above that, for example 130 seconds. Each account can run up to 100 requests at once, across all four ways in.
A minimal API request looks like this:
const response = await fetch("https://app.dinproxy.com/api/unblocker/request", { method: "POST", headers: { Authorization: "Basic " + Buffer.from("USERNAME:PASSWORD").toString("base64"), "Content-Type": "application/json", }, body: JSON.stringify({ target_url: "https://example.com", country: "us" }), signal: AbortSignal.timeout(130_000),});
const result = await response.json();console.log(result.data.html);Replace USERNAME and PASSWORD with a proxy user, such as 1024~myuser. The reply is JSON with the page's HTML in data.html. The API reference lists every parameter.
How each is billed
The two products charge for different things, and that difference often decides the choice.
Residential proxies are billed per GB of traffic. You buy GB in the dashboard, and your traffic through the proxy draws on that balance. Purchased traffic never expires, so you can buy once and use it over time. What you spend follows how much data your pages use.
The Web Unlocker is billed per successful result. Results are sold in units of 1,000. Each successful request uses one result, whatever the response format, and failed requests use nothing. JavaScript rendering and screenshots cost nothing extra, so what you spend follows the number of pages you receive, not their size.
Both products are paid from the same prepaid Credits balance. Once bought, the traffic or results sit in the product's own balance.
Side-by-side comparison
| Residential proxies | Web Unlocker | |
|---|---|---|
| You send | Your own requests, through the proxy | A target URL and options |
| You get back | The site's response, in your own client | The page as HTML, a PNG screenshot, or both |
| JavaScript rendering | Done by your own browser or tool | Built in, on by default |
| CAPTCHAs and anti-bot checks | Handled by your own setup | Handled inside the request |
| Location | Country, state and city | Country |
| Sessions | Rotating, or sticky for up to 120 minutes | Proxy routing managed for you |
| Ways to connect | HTTP, HTTPS or SOCKS5 proxy | API, proxy mode, MCP server, command-line tool |
| Sign-in | Proxy user or whitelisted IP | Proxy user |
| Billing unit | GB of traffic | Successful results, sold per 1,000 |
Which jobs suit each
Use residential proxies when:
- You already run a scraper or browser, and your targets answer well-paced requests with realistic headers.
- The job includes a login, a cart or another multi-step flow, where your client keeps cookies and state across pages on a sticky session.
- You need state- or city-level locations.
- You make many light requests, such as JSON endpoints or plain HTML pages, where per-GB billing suits the volume.
- Your tool connects over SOCKS5.
Use the Web Unlocker when:
- Pages sit behind CAPTCHAs or anti-bot checks such as Cloudflare, DataDome, PerimeterX or Imperva.
- The content appears only after JavaScript runs, and you would rather not operate headless browsers.
- You want a screenshot of the page as well as, or instead of, its HTML.
- You want an AI assistant such as Cursor, Claude or VS Code to read pages through the MCP server.
- You prefer to pay per page you receive, with failed attempts free.
Using both together
The two products work well side by side. The same proxy users sign in to residential proxies, mobile proxies and the Web Unlocker, so one set of credentials covers every job.
One pattern is to send pages through residential proxies by default and move a target to the Web Unlocker once it starts answering with CAPTCHAs or bot checks. Proxy mode keeps that switch small: point the scraper at unblocker.dinproxy.com:7780 instead of proxy.dinproxy.com:7777, with the same proxy user. For HTTPS pages, also have the scraper trust the DINPROXY Web Unlocker certificate or skip the certificate check for that proxy.
Another is to split one site by page type. Crawl listing and search pages with rotating residential IPs, which suit many independent requests, and fetch the protected detail pages with the Web Unlocker.
Before reaching for either, the basics still pay off: realistic headers, steady pacing and the right location. Our guide on how to scrape a website without getting blocked covers them, and rotating vs sticky residential proxies explains the session choice. If you would rather receive the data than collect it, Web Datasets delivers ready-made or custom datasets as files.
Frequently asked questions
Per successful result: each successful request uses one result, whatever the format, and failed requests use nothing. Results are sold in units of 1,000.
Per GB of traffic. Purchased traffic never expires, so you can use it whenever you like.
Yes. The same proxy users sign in to residential proxies, mobile proxies and the Web Unlocker. The Web Unlocker always signs in with a username and password.