# CurlShot Review

Screenshot API for developers: turn any URL, HTML, or Markdown into a PNG, PDF, or scrolling video with one HTTP request.

## Editor's Score: 68/100

Capability scores well because the feature set is genuinely broad for a focused API: eleven distinct capabilities including MCP server support, bulk runs of up to 100 URLs, async webhooks, CSS-selector element capture, and seven output formats, with no comparable MCP-native screenshot tool in this directory. Ease of use is strong on paper: one GET request, no SDK, code examples in six languages, an OpenAPI 3.1 spec, and an llms.txt file all lower the integration barrier significantly. Value is decent but not exceptional: $19/month for 3,000 screenshots is competitive, the free tier requires no card, and the overage cap prevents bill shock, but the free plan's single concurrent render and 100-screenshot ceiling make it nearly useless for real production testing. Delivery scores low because the product is days old at review time, all public submissions were made by the maker with no independent user validation, there is no documented uptime SLA, and no third-party sentiment exists to confirm the API performs as described. A tool this new with zero independent evidence of reliability cannot score above the low teens on delivery.

## Pros
- Hosted MCP server at a fixed endpoint means AI agents in Claude or Cursor can call take_screenshot with zero infrastructure setup, a feature no comparable screenshot API in this directory offers.
- Quota billing counts only successful renders: failed renders and cache hits are free, and optional overage is off by default with a user-set cap, so surprise bills are structurally prevented.
- Broad output coverage in one API: PNG, JPEG, WebP, PDF, MP4, WebM, and GIF from a URL, raw HTML, or Markdown, with CSS-selector element capture and bulk runs of up to 100 URLs per call.

## Cons
- The free plan allows only one concurrent render and 10 requests per minute, which makes it genuinely unsuitable for anything beyond a proof of concept; even a modest production app will hit the ceiling within hours of a traffic spike.
- No documented uptime SLA, no public status page mentioned in any available source, and no enterprise support tier, which is a real gap for teams where screenshot availability is on the critical path.
- The tool is very new and submitted by its own maker across multiple directories simultaneously, so independent user reviews, long-term reliability data, and community sentiment are essentially absent.

## Pricing

Freemium. A free tier is available.
- Free: $0
- Starter: $19/month
- Growth: $79/month
- Scale: $249/month

Pricing reflects what we saw at the time of review (2026-10). Confirm current pricing on the official site.

Category: AI Coding & Dev Tools (https://aitoolseekers.com/category/ai-coding-dev-tools)
Official site: https://curlshot.com/
Last verified by a human: 2026-10-23

Reviewed by a human at AI Tool Seekers, a hand-reviewed AI tools directory. Every listed tool is verified by a person before publishing. Scores are editorial opinions from a fixed rubric (capability, ease of use, value, delivery on promise) and cannot be bought; there is no pay-to-rank.
Directory: https://aitoolseekers.com
This review: https://aitoolseekers.com/tools/curlshot
Methodology: https://aitoolseekers.com/how-verification-works

## Verdict

CurlShot is the right pick for developers and AI agent builders who need a hosted, no-infrastructure screenshot service with native MCP support for tools like Claude and Cursor. Its pricing is transparent and quota-based, but the free tier's 100 screenshots per month and single concurrent render will hit a ceiling fast for anything beyond prototyping. Teams needing general-purpose AI coding assistance rather than a screenshot API should look at GitHub Copilot instead.

Best for: Developers and AI agent builders automating web captures at scale
Not for: General AI coding assistance or teams without a programmatic screenshot use case

## Overview

CurlShot is a hosted screenshot API: one GET request to its endpoint returns a PNG, JPEG, WebP, PDF, or a scrolling video (MP4, WebM, GIF) of any URL, HTML string, or Markdown document. Pages render in a real browser, so lazy-loaded images appear and the layout matches what a visitor actually sees. The differentiator that sets it apart from older screenshot APIs is a hosted Model Context Protocol server at a fixed endpoint, meaning AI agents running inside Claude, Cursor, or any other MCP client can call take_screenshot directly without the developer writing any glue code or running a headless browser themselves.

The feature set goes beyond a simple URL-to-image pipe. You can capture a single DOM element by CSS selector, switch between phone, tablet, and desktop viewport presets, enable dark mode, and strip cookie banners, ads, and chat widgets before the shot is taken. Bulk runs accept up to 100 URLs per call, async jobs return results via signed webhooks, and the API ships with an OpenAPI 3.1 spec plus an llms.txt file so tool-discovery for agents works out of the box. An n8n community node covers no-code automation pipelines.

Pricing is quota-based and unusually honest: failed renders and cache hits do not count against the monthly allowance. The free plan gives 100 screenshots per month with no credit card, one concurrent render, and 10 requests per minute. Paid tiers scale from 3,000 screenshots at $19/month up to 60,000 at $249/month, with optional overage that is off by default and capped at a ceiling the user sets.

CurlShot is a young, focused commercial product built by a small team. The GitHub repositories are public and the maker is transparent about being the submitter across directory listings. There is no public information about funding, headcount, or enterprise SLAs, which matters if uptime guarantees are a hard requirement.

## Who should use it

CurlShot fits a backend developer who needs to generate link previews, open-graph cards, or PDF exports from HTML templates without running and maintaining a headless browser fleet. It also fits an AI agent developer who wants their Claude or Cursor workflow to visually verify a deployed page or capture evidence from a URL, since the MCP server removes the need to write any integration layer.

Docs teams automating screenshot refreshes in CI pipelines are another natural fit, as are small agencies running visual regression checks across phone and desktop viewports. If you need a general-purpose AI coding assistant that helps you write, refactor, or review code rather than capture web pages, CurlShot is the wrong tool entirely. GitHub Copilot covers that use case and is already in this directory. If your screenshot volume is very high and you need enterprise SLAs or a self-hosted option, CurlShot's current Scale plan tops out at 60,000 screenshots per month with no documented uptime guarantee, so you should contact the team or evaluate alternatives before committing.

## FAQ

Q: Does a failed render count against my monthly screenshot quota?
A: No. Only successful renders count. Failed renders and requests answered from the cache are free on all plans, including the free tier.

Q: What happens when I hit my monthly limit?
A: The API returns a clear error (HTTP 402) and stops processing requests until the next billing period starts. On paid plans you can pre-enable overage at $8, $5, or $4 per extra 1,000 screenshots (Starter, Growth, Scale respectively), with a monthly cap you set yourself so spending cannot exceed what you chose.

Q: How do I connect CurlShot to Claude or Cursor?
A: Point your MCP client at the hosted endpoint (curlshot.com/api/mcp) and add your API key. Nothing needs to be installed locally. The server exposes two tools: take_screenshot and list_devices.

Q: Can I render my own HTML or Markdown, not just external URLs?
A: Yes. You can POST raw HTML or Markdown and receive a PNG, JPEG, WebP, or PDF back. This covers use cases like social card generation, invoice rendering, and certificate exports.

Q: Is there a free plan, and does it require a credit card?
A: The free plan gives 100 screenshots per month with no credit card required. It is permanent, not a trial, though it limits you to 1 concurrent render and 10 requests per minute.

Q: Does yearly billing change the monthly screenshot allowance?
A: No. The screenshot allowance still resets every month on a yearly plan. Yearly billing saves roughly two months of cost (for example, $190/year versus $228 paid monthly for Starter) but does not increase the per-month quota.