WS WebScraperStudio Public content layer for scraping buyers
Home/Docs/Developers/Scraper API vs Scraper Studio

Developers

Scraper API vs Scraper Studio

Updated July 1, 2026 This is the internal decision boundary that matters most once a buyer has moved beyond content discovery and into implementation design.

Prebuilt Dataset Lane

Use the prebuilt lane when the target is already modeled, the host is allowed, and the data shape is close to an existing public template. This is the lowest-friction route and the safest public action path.

Custom Collector Lane

Use the custom collector lane when the host is not modeled, the field set is custom, or the job needs a managed implementation with tighter control over scope and change handling.

Practical Rule of Thumb

If a buyer can validate the job with one representative URL and a known host, stay on the prebuilt path. If the buyer is already discussing scale, custom extraction, or unsupported targets, move them into diagnostics and treat the collector path as admin-owned work.

Next action

This is the internal decision boundary that matters most once a buyer has moved beyond content discovery and into implementation design.

Request implementation review Compare provider paths

Frequently asked questions

Why not expose custom collectors publicly?

Because that would collapse the operational boundary between content discovery and managed implementation into an anonymous public workflow.

Does every unsupported host require Scraper Studio?

Not always, but unsupported hosts are a strong signal that a public template is not enough and diagnostics should own the next decision.

Related guides

Developers

API Boundary

The public site owns discovery and content. The backend owns credentials, live runs, lead capture, and provider jobs.

Getting Started

How Diagnostics Works

Use diagnostics when the public scraper surface is not enough and the request needs routing, scoping, or managed review.

Continue with

Ecommerce

Amazon Product Monitor

The safest public Bright Data demo: one product URL in, a truncated product preview out.