Hosted browser API
Scrnify vs Microlink: screenshot API comparison
Scrnify is for developers who want screenshot and video Captures through one API or CLI with metered usage. Microlink is stronger when you need a broader browser API for screenshots, PDFs, metadata, link previews, markdown, and structured page output.
| Criteria | Scrnify | Microlink |
|---|---|---|
| Pricing model | Graduated: 0.008 EUR for first 2,000 billable units per billing period, then 0.005 EUR for units above 2,000; no fixed monthly fee | Free tier, monthly quota plans, and Enterprise |
| Free usage | 100 lifetime units; 100 units per Stripe billing period with active billing | 50 requests/day on the free plan |
| CLI | Homebrew CLI for terminal and CI | npm-installed CLI for inspecting screenshots, metadata, PDFs, timing, headers, and JSON payloads |
| Video | First-class Capture type; priced by second | Animated recordings are available, but core positioning is broader URL-to-output browser API |
| API breadth | Screenshot and video Captures | Screenshots, PDFs, metadata, link previews, markdown, logos, search, Lighthouse insights, and cache controls |
| SDKs and docs | HTTP API and CLI today | SDK, CLI, cURL, JavaScript, Python, Ruby, PHP, and Go examples |
| Best fit | CI, terminal workflows, simple metered pricing, screenshot/video Capture | Broad URL-to-output workflows, link previews, PDFs, metadata extraction, and mature public docs |
Choose Scrnify when
You want simple metered pricing, CLI-friendly Captures, and one Capture model for screenshots and videos.
Choose Microlink when
You need a mature browser API that turns URLs into several output types beyond screenshots, including PDFs, metadata, markdown, and link previews.
Migration path
Start with screenshot Captures that only need URL, viewport, and output format. Keep Microlink for workflows that depend on metadata, previews, PDFs, markdown, proxy resolution, or custom cache behavior until those needs are mapped.