Byteful✓

Measure the workload before you buy data 📊 Counting requests gives a rough guess. Measuring data per successful result is what to size a tier on, since payload, rendering and retries are already in it. Residential and mobile data does not expire on Byteful.

Test a proxy from where you will actually use it 🌍 Our proxy tester runs the same proxies from servers across the US, Europe and Asia at once, against a target you choose. Results per region, with status codes. Works on any provider's proxies. Free, no account needed.

Byteful shows how many mobile nodes match before you generate anything 📍 Pick a country, region, city or carrier and the dashboard updates a live count of nodes currently online and matching. Same data in the public API, so an automated job can check before it runs.

AI agents count on us for web access. We count on you for uptime 🤝

@PicapLatam @ProbablyDatabot @byteful hosts its website and dashboard on App Platform, with managed Postgres replicated near the edge and automatic failover behind it.

One missing colon can stop a proxy list importing 🔧 Our proxy formatter converts a whole list at once. Paste or upload, it works out the source format on its own, you pick the output, then copy or export. It rewrites the list. It will not tell you which proxies are live.

Free, no account needed:

The Byteful Startup Program is live🚀 Free residential data for three months, then up to 50% off for two years. Three tiers for bootstrapped, VC or accelerator backed, and Y Combinator companies. Plus a Slack channel with a senior Byteful developer.

Full eligibility and the application forms:

Ten questions worth asking any proxy provider before you buy 📋 How are they billing you, and what counts? Does unused data expire? How long does a sticky session really last? What is the P95, not the average? When a request fails, are you told why? Five more in the carousel.

A scraping job that works at 100 requests does not automatically work at 100,000 📋 1️⃣ Data consumption at volume 2️⃣ Your timeout 3️⃣ Your concurrency ceiling 4️⃣ Retry strategy, with backoff 5️⃣ Whether you can tell why something failed

Introducing TCP/IP Fingerprint Emulation, now live in beta on datacenter and ISP proxies! Your browser says Windows. Does the TCP handshake agree? 💻 Windows, macOS, Linux, Android or iOS, set per request in your proxy username or once when you export your list.

Full details:

RT @zytedata: Your TCP handshake can give away which OS you run, whatever your User-Agent says. Joe Dye of @byteful takes #ExtractSummit2026 down to the packets. #WebScraping #Proxies

Day two of @zytedata's Extract Summit is underway, and Byteful is here in Austin, Texas! Today at 12:00pm, our founding engineer Joe Dye takes the stage at Brazos Hall for a talk on TCP/IP fingerprint emulation🫆 Come and say hello before or after👋

Byteful accounts now support organizations 👥 A shared workspace for your team with its own proxies, billing and API keys. Each member gets a role, so no more sharing one password. API keys can be scoped to specific actions with an expiry date, which is what you want when an agent holds the key.

Scheduled maintenance from 9 to 11am BST today 🛠 During this window, API services will be intermittently accessible and the dashboard may be temporarily unavailable. Existing proxies will continue to work as normal. Live status:

We've extended this window by one hour, to midday BST today⏰ This change is to ensure as minimal disruption as possible to our API. Proxy network services remain unaffected during the window.

Unlimited concurrent sessions means there is no concurrency tier to buy 🔓 No plan-level cap to hit, no upgrade to reach for. You pay for data or for IPs, not for how many requests run at once. Fair usage safeguards still exist for traffic that threatens stability. Rarely triggered.

Smartpath decides in under 10ms whether a request actually needs a residential IP. If it does, it uses residential. If it does not, the request can go through datacenter instead without consuming residential data. Most request latency comes after that routing decision.