Skip to main content

Confirm

Are you sure?

URLpipe vs ScreenshotOne

URLpipe vs ScreenshotOne

ScreenshotOne is a screenshot specialist; URLpipe takes screenshots as one of eight kinds of data about a URL. Both run async with signed webhooks and both have a hosted MCP server.

By · Last updated: September 2026

TL;DR

Choose ScreenshotOne when screenshots are the product: more formats, video, GPU rendering, chat and tracker blocking, SDKs in seven languages. Choose URLpipe when the screenshot is one of several things you need about a page — Markdown, metadata, Lighthouse, console errors — or when processing must stay in Europe.

Free plan, no credit card. 1,000 credits a month.

At a glance

Feature by feature

CapabilityURLpipeScreenshotOne
Clean Markdown from a URLYesYes
Renders JavaScript (real browser)YesYes
Rendered HTMLYesYes
ScreenshotsYesYes
Full-page screenshotsYesYes
Element, dark-mode and hidden-selector screenshotsYesYes
Metadata / Open GraphYesYes
AI summaryYesVision prompt, your OpenAI key
Keyword extraction endpointYesNo
Lighthouse auditsYesNo
JavaScript console captureYesNo
Several outputs from one page visit/scrapePartial
Whole-site crawlingNoNo
Schema-based structured extractionNoNo
PDF input or outputNoOutput
MCP serverHostedHosted, or npx
Async + webhook for a single URLYesYes
Idempotency key on retriesYes—
Your own labels on requests, usage by labelYes—
Cached results cost nothingYesYes
Residential-IP fetchingOne exit, +25 credits/visitNo
Official SDKsNo7 languages
Self-hostableNoNo
Free tier1,000 credits/mo100 renders/mo
EU processing, AI includedYes—

ScreenshotOne: checked against screenshotone.com/pricing, screenshotone.com/docs/options, screenshotone.com/integrations/mcp, screenshotone.com/privacy-policy on September 24, 2026. Products change — confirm on each vendor's site before you decide.

Common ground

What they share

Full-page capture, one element by selector, dark mode, ad and cookie-banner blocking, hidden selectors and injected CSS; async requests delivered to signed webhooks; failed and cached captures free; a hosted MCP server. For most screenshots, either will do.

Its strengths

Where ScreenshotOne goes further

  • Formats: AVIF, HEIF, GIF, TIFF, JP2 and PDF as well as PNG, JPEG and WebP.
  • Video and scrolling captures, from the Growth plan.
  • Blocking for chats and trackers, and heuristic banner blocking.
  • Device scale up to 5×; GPU rendering on Scale.
  • SDKs for Go, Java, PHP, Ruby, Python, .NET and JavaScript.

Ours

Where URLpipe goes further

  • The rest of the page: Markdown, metadata, a summary, keywords, Lighthouse and console errors — several from one visit with /scrape.
  • Europe: fetching, rendering and storage in the EU on every plan, AI processing EU-only per organization. ScreenshotOne's privacy policy says it is not yet GDPR-compliant.
  • Results kept at a token for 30 days, as well as delivered to a webhook.
  • Idempotency keys, labels per customer, and a residential exit per request.
URLpipe screenshot with options
curl -X POST https://urlpipe.dev/screenshot \
  -H "Authorization: Bearer $URLPIPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com",
    "sync": true,
    "page_options": { "block_ads": true, "block_cookie_banners": true },
    "screenshot_options": {
      "format": "webp",
      "viewport_width": 390,
      "device_scale_factor": 2,
      "dark_mode": true,
      "hide_selectors": ["#chat-widget"]
    }
  }'

Billing

What a capture costs

ScreenshotOne counts successful, uncached renders against a monthly allowance, and bills extra only if you turn overage on, under a cap you set. URLpipe counts credits — 1 per screenshot whichever options you use — and a paid plan carries on past its allowance at $1.50 per 1,000 credits. Heavy pages cost the same on both: URLpipe caps the dear dimensions (a delay and a wait of 10 seconds at most, one 16,384 px surface) instead of metering them.

A result served from cache costs nothing (max_age defaults to 7 days, up to 30); an identical request that arrives while the first is still running waits for it and costs nothing; an Idempotency-Key makes a retry return the first result; and bot checks we couldn't clear, target 4xx/5xx pages and robots.txt refusals are never billed.

Pricing

What each one costs

URLpipeScreenshotOne
Free tier$0 — 1,000 credits/mo, no card$0 — 100 screenshots/mo, no card
Entry paid planStarter $19/mo — 20,000 creditsBasic $17/mo — 2,000 screenshots
Mid planPro $49/mo — 55,000 creditsGrowth $79/mo — 10,000 screenshots
Billing unitCredits per call: Markdown, HTML, screenshot or console 1, Lighthouse 2, metadata 5Successful, uncached renders
OveragePaid plans never cut off — $1.50 per 1,000 creditsOpt-in, $0.009 each on Basic, under a monthly cap you set
Cache hitsFree, up to 30 days oldFree

ScreenshotOne Basic is $17 for 2,000 screenshots; URLpipe Starter at $19 is 20,000, every option included.

Who it's for

An honest recommendation

Choose URLpipe if…

  • You need the page's content and health alongside its screenshot
  • Processing must stay in Europe
  • You want results collectable by token as well as by webhook
  • PNG, JPEG or WebP up to 3× is enough

Choose ScreenshotOne if…

  • Screenshots are your whole product
  • You need video, AVIF, GIF or PDF output
  • You want an SDK in your language
  • You need GPU rendering or 5× scale

Moving off ScreenshotOne?

What switching involves

The ScreenshotOne alternatives page covers why people leave, what to look for instead and how the requests map.

FAQ

Frequently asked questions

Which is better for screenshots, URLpipe or ScreenshotOne?
For screenshots alone, ScreenshotOne has more options, formats and video. URLpipe is better when you also need the page's Markdown, metadata, Lighthouse or console errors, or EU processing.
Do both support async screenshots with webhooks?
Yes. ScreenshotOne takes async=true with a webhook_url; URLpipe is async by default and also keeps the result at GET /result/:token for 30 days.

Try URLpipe on the free plan.

1,000 credits a month, no card. Confirm your email and your key is live — most people make their first request inside five minutes.