Web Scraper Proxy Setup with a German Mobile Proxy

Direct Answer

Web Scraper has two modes. The browser extension has no proxy field of its own — it scrapes through whatever IP your browser uses, so you set the German mobile proxy at the browser level (e.g. with FoxyProxy). Web Scraper Cloud runs jobs server-side and supports a custom proxy on the Scale plan.

Which Mode Are You Using?

This matters because the proxy lives in a different place:

Web Scraper browser extension (free, local): the scrape runs inside your Chrome/Firefox tab. There's no separate proxy setting — point the browser at your German mobile proxy and the extension follows.
Web Scraper Cloud (paid): jobs run on Web Scraper's servers. Its built-in proxy option rotates IPs (US-based, every 5 minutes) only when you enable it; the custom proxy setting — available on the Scale plan — instead routes cloud jobs through your own German mobile IP.

You'll need from your GermanProxy.io account: host, port, and username/password (or a whitelisted IP).

Extension — Set the Proxy at Browser Level

Install a browser proxy switcher such as FoxyProxy — see our FoxyProxy browser extension guide for the exact steps.
Add your German mobile endpoint (host, port, username, password) as a FoxyProxy profile.
Switch it on, then run your Web Scraper sitemap as usual. The extension scrapes through the browser's active proxy.

Honest note: this routes all matching browser traffic through the proxy while active, not just Web Scraper. That's expected for browser-level proxying — see the FoxyProxy guide for scoping with URL patterns.

Web Scraper Cloud — Custom Proxy

Open your sitemap in Web Scraper Cloud and go to the scraping-job / proxy settings.
Select the custom proxy option (available on the Scale plan) and enter your German mobile endpoint.
Save and start the job; cloud requests now exit through your German mobile IP.

Cloud's default IPs are US-based; a custom proxy is what gives you a true German mobile vantage point.

Verify the IP First

Build a one-page sitemap that reads an IP-echo site (e.g. https://api.ipify.org) and run it. The captured value should be a German mobile IP. For the extension, confirm FoxyProxy is active; for Cloud, confirm the custom proxy is selected on the job.

Sticky Sessions vs. Rotation

A single dedicated German endpoint keeps a stable IP across a sitemap; rotate on demand at the proxy when you want to spread load. The country stays German either way. See sticky sessions and IP rotation explained.

Scrape Responsibly

A mobile proxy improves reliability for legitimate data collection — it is not a tool to circumvent access controls or platform rules. Respect each site's robots.txt and terms, keep request rates reasonable, collect only what you need, and handle any personal data in line with the GDPR. For the legal side, see is web scraping legal? EU & GDPR.

FAQ

Does the Web Scraper extension have a proxy setting?

No. The extension scrapes through your browser's connection, so set the proxy at browser level (e.g. FoxyProxy). Web Scraper Cloud is the mode with a built-in custom-proxy option.

Is the custom proxy free?

The custom-proxy setting in Web Scraper Cloud is available on the Scale plan; the local browser extension is free but relies on your browser's proxy.

Will browser-level proxying affect my other tabs?

While active, FoxyProxy routes matching traffic through the proxy. Use its URL-pattern rules to limit which sites are proxied — covered in the FoxyProxy guide.

HTTP or SOCKS5?

Browser switchers and Web Scraper Cloud both accept standard proxy endpoints. See HTTP or SOCKS5 — which fits your stack.

Related guides

CTA

Give Web Scraper a real German mobile IP. Get your German mobile endpoint — HTTP/SOCKS5/OpenVPN, sticky sessions, fair-use 20 GB/day.

Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — see German 4G/5G mobile proxy options or get a dedicated proxy on the Blue network.