Render anything. Instantly.
Render your HTML charts, reports, and pages to an image or PDF.
From a URL or Markdown too — one POST to a rendering API built for automation. Wire it into n8n, Make, Zapier, or any AI agent over MCP. Signed webhooks, batch, and 300+ edge locations.
Free · no credit card · 100 renders/mo
Live · edit the HTML and hit Render
n8n · cron · agentPOST /v1/screenshotPNG · PDF → report · S3 · email
→
Output · PNG · 1200×630200 OK · png · 211 ms
Built for teams like yours
SaaS Platforms
Marketing Teams
QA Engineers
AI Startups
Agencies
Dev Tool Companies
SaaS Platforms
Marketing Teams
QA Engineers
AI Startups
Agencies
Dev Tool Companies
SaaS Platforms
Marketing Teams
QA Engineers
AI Startups
Agencies
Dev Tool Companies
SaaS Platforms
Marketing Teams
QA Engineers
AI Startups
Agencies
Dev Tool Companies
Call → render → image. Three steps, no detour through a browser farm you have to manage.
POST your payload, get bytes back. Same engine across every plan, every region, every interface — REST, SDK, or MCP.
STEP 01CallPOST to /v1/screenshot with HTML, URL, or Markdown — plus an optional data{} object to fill templates.
curl https://api.rendex.dev/v1/screenshot \
-H "Authorization: Bearer $KEY" \
-d '{"markdown":"# Invoice {{n}}","data":{"n":"A-100"},"format":"pdf"}'STEP 02RenderHeadless Chromium on the edge nearest your caller.
{ "engine": "chromium-124", "edge": "iad", "took_ms": 211 }No infra to provision. No browsers to crash-loop. We retire workers between requests so one bad page can't poison the next.
STEP 03GetStream back PNG/PDF, redirect to a signed URL, or webhook.
HTTP/1.1 200 OK Content-Type: image/png Content-Length: 84321 X-Rendex-Edge: iad · X-Rendex-Took-Ms: 211
n8n, Make, Zapier, MCP — the four ways most Rendex calls actually start.
Drop into an existing workflow without writing code, or call from any HTTP-aware tool.
n8n community node
Official n8n node with HTML, URL, and Markdown render modes — plus 10 ready-made workflow templates you can import in one click.
↳ DROP-IN STEPMake HTTP module
Pre-built HTTP scenario template — render HTML, a URL, or Markdown, then pipe the image or PDF into Drive, Slack, or Notion.
↳ TEMPLATEZapier action
Native Zapier action with rendering presets — social card, thumbnail, full-page capture, PDF report, OG image — from HTML, a URL, or Markdown.
↳ NATIVE ACTIONMCP
Model Context Protocol
One-line MCP endpoint so Claude, Cursor, and any MCP-aware agent can render images and PDFs as a tool call.
↳ TOOL ENDPOINTOne MCP endpoint — Claude, Cursor, and your own agents render in a single tool call.
Same render engine, exposed as MCP tools your agent runtime already understands.
For AI agents
Give your agent a render tool, not a browser farm.
MCP is how Claude, Cursor, and other agent runtimes load external tools. Rendex exposes its render engine as MCP tools — your agent gets render_artifact, rendex_screenshot, rendex_extract and more, instantly.
- Arender_artifact — Markdown or HTML → a branded PDF, PNG, and hosted share link in one call — built for agent outputs.
- Srendex_screenshot — HTML, Markdown, or URL → image or PDF. Same viewport, waitForSelector, and format options as REST.
- Erendex_extract — URL → clean reader-mode Markdown, JSON, or article HTML, pulled from the fully-rendered DOM.
- +render_link · account · watch — Mint hosted render links, check plan + usage in-chat, and monitor pages for changes — 13 MCP tools in all.
{
"mcpServers": {
"rendex": {
"url": "https://mcp.rendex.dev/mcp",
"headers": {
"Authorization": "Bearer $RENDEX_KEY"
}
}
}
}13 tools · render_artifact · screenshot · extract · watchv1
Seven things — picked because they matter, not because we needed to fill twenty-five tiles.
Render, PDF, Markdown & templating, hosted URLs, extraction, batch, reliability. Tab through what you care about.
1
HTML → image
Raw HTML in, PNG or JPEG out. ~95% of real Rendex traffic. Custom viewport, retina @2x, dark-mode emulation.
2
URL → image
Point at any URL. waitForSelector, networkidle wait, ad + cookie-banner blockers.
3
Full-page capture
Scroll-stitched screenshots up to 16,384 px tall.
4
Device presets
One device field — iphone_15, pixel_8, ipad — sets viewport, scale, and user-agent for you.
5
Resize & thumbnails
Downscale the output with resizeWidth / resizeHeight — aspect ratio preserved when you set just one — straight into an <img src> thumbnail.
render.config.json
{
"html": "<…>",
"format": "png",
"device": "iphone_15",
"waitForSelector": "img.hero",
"fullPage": true,
"blockCookieBanners": true,
"hideSelectors": [".chat-widget"],
"resizeWidth": 600
}Desktop crop · 1200×630image/png · @2x
Full-page · 1200×4200scroll-stitch
Render · responsive pageone `device` field · viewport + scale + UA
Device presets · one `device` fieldiphone_15 · 393×852 · @3x · real UA
Add a capability, watch it land three ways at once.
Point Rendex at a URL and toggle a capability. The result reshapes, the request grows a highlighted line for developers and AI agents, and the matching field lights up in a no-code node for n8n, Zapier, and Make. Same API, shown the way each person actually works.
DeviceAdd capabilities
Resultpng · 1280×800 · @2x
AD PLACEMENT · 728 × 90
200 OK · image/pngrender 150 ms
Request bodyPOST /v1/screenshot
{
"url": "https://northwind.io",
"width": 1280,
"height": 800,
"format": "png",
}
New Rendex Watch
Now it watches pages too, not just renders them.
Point Rendex Watch at any URL and get a real-Chrome before/after visual diff with a highlighted overlay — alerts by email (every plan) or webhook (Starter+). Create a watch point-and-click in your dashboard or with one API call, on the same rdx_ key and credit pool.
status.northwind.iowatch.changed
6.7% changed · 3 regionsbefore → after → overlay
Built for production & EU teams
GDPR-readyDPA on requestNo HTML stored on standard rendersSSRF + Safe BrowsingVAT invoicesPrivacy & DPA →
Pick your throughput. Unlock the capabilities you need.
Four tiers, separated by speed (requests/min) and what each unlocks. Hitting rate limits on Free? Basic is 3× faster. Every plan is a hard cap — no overage, no surprise invoices, ever. Monthly or annual (2 months free yearly); EU VAT and B2B reverse-charge are captured at checkout.
USD · throughput + capability
Free
$0/ mo
3req / min100 renders / mo
Build, test, ship a prototype. Same engine, same edge — capped at 3 requests/min. Hitting the rate limit? Basic is 3× faster.
- Calls / mo100
- Req / min3
- URLs / batch—
- Concurrent3
- API keys1
- Geo-target—
- Watches1 (daily)
- WatermarkTiled mark
Basic
$12/ mo
or $10/mo billed annually — 2 months free10req / min400 renders / mo
Go to production without overpaying. 3× the throughput of Free, plus authenticated rendering — cookies, headers, logged-in pages — clean watermark-free output, and batch. For solo builders and small automations before you scale to Starter.
- Calls / mo400
- Req / min10
- URLs / batch5
- Concurrent5
- API keys2
- Geo-target—
- Watches2 (every 3 hr)
- WatermarkNone
Regional pricing in your country — see credit packs below.
Get Basic →Starter — Recommended
$69/ mo
or $58/mo billed annually — 2 months free60req / min10,000 renders / mo
Automate for a team. Completion webhooks and real volume — 10,000 renders a month at 60 req/min, bigger batches, and every endpoint on one key.
- Calls / mo10,000
- Req / min60
- URLs / batch25
- Concurrent50
- API keys5
- Geo-target—
- Watches10 (hourly)
- WatermarkNone
Regional pricing in your country — see credit packs below.
Get Starter →Pro
$179/ mo
or $149/mo billed annually — 2 months free300req / min100,000 renders / mo
Scale and advanced delivery. 300 req/min, geo-targeting from 50+ countries, your own S3/R2 storage, and high concurrency for heavy production workflows.
- Calls / mo100,000
- Req / min300
- URLs / batch100
- Concurrent200
- API keys10
- Geo-target50+ countries
- Watches50 (every 30 min)
- WatermarkNone
Regional pricing in your country — see credit packs below.
Get ProCredit packs — $5 · 500 renders
A one-time top-up for when you just need a few more renders — no subscription, credits never expire, and they work on any plan, including Free. Some countries get lower-priced regional packs (smaller sizes, from $2).
Enterprise
Higher limits, custom SLA, unlimited calls, and up to 1,000 website watches at 5-minute checks for teams running rendering at scale. We'll size a plan to your volume.
The questions we actually get from devs and automation builders.
Short answers, real code snippets, no marketing.
01How does the free tier work?
You get 100 API calls per month, forever. No credit card required to sign up. The free tier never expires — it's designed to let you evaluate the API and build prototypes without any commitment. Free renders carry a light "rendex.dev" watermark tiled across the image (a footer line on PDFs) — your content stays readable underneath. Every paid plan — starting with Basic ($12/month) — is fully watermark-free.
02What's the difference between Rendex and a screenshot-only API?
Rendex is a rendering platform — not just a screenshot tool. Beyond URL screenshots, it handles PDF generation, HTML-to-image rendering, URL→Markdown extraction, hosted render links (og:image), batch processing, async webhooks, geo-targeted capture, website change monitoring (Rendex Watch), and MCP integration for AI agents. One API, one key, one billing relationship for all your rendering needs.
03Can I render HTML to an image without hosting a page?
Yes. Pass raw HTML via the "html" parameter instead of a URL. Rendex renders it to PNG, JPEG, WebP, or PDF. Generate social cards, invoices, OG images, and email previews — all without hosting a page. Full CSS support including Flexbox, Grid, and Google Fonts.
04Can I render Markdown to an image or PDF?
Yes. Pass your content via the "markdown" parameter and Rendex converts it to a styled HTML document with GitHub-flavored typography, then renders it to PNG, JPEG, WebP, or PDF — no CSS or hosted page required. It is the fastest path for AI agents (which emit Markdown natively), READMEs, changelogs, and release notes. The markdown parameter is mutually exclusive with url and html.
05Can I generate PDFs from URLs or HTML?
Yes. Set "format": "pdf" on any request to render a URL or raw HTML to a paginated PDF. You can configure page size (A4, Letter, custom), margins, orientation, scale, and background printing. Perfect for reports, invoices, and documentation — no wkhtmltopdf or Puppeteer needed.
06Can I generate PDF invoices or reports from a template?
Yes. Send a "data" object alongside your HTML or Markdown and Rendex renders it as a logic-less Mustache template before capture, filling {{placeholders}} from your data. Use {{#items}} to loop over line items and {{a.b}} for nested values; values are HTML-escaped by default. Add "format": "pdf" and one reusable template plus a data object becomes a paginated invoice, report, certificate, or card — ideal for no-code automations and AI agents. Templating is valid only with html or markdown (combining data with a url returns a 400).
07Can I render a dashboard or report to a scheduled PDF?
Yes, by pairing Rendex with any scheduler. Rendex renders a live dashboard or report — a URL (with cookies or auth headers on paid plans for gated pages) or your own templated HTML — to a paginated PDF on demand via "format": "pdf". To run it on a schedule, trigger that render from a cron job, n8n, Make, or Zapier (for example, every morning) and route the PDF to email, S3, or Slack in the next step. Rendex itself doesn't keep a report calendar — the schedule lives in your automation tool, so you keep full control of timing and delivery.
08Can I get an OG image as a hosted URL instead of bytes?
Yes. POST your render to /v1/render/link and Rendex returns a signed URL you drop straight into <meta property="og:image"> or an <img src> — no backend or storage on your side. The first request renders and caches it on the edge; every repeat (every crawler, every share) serves the cached copy, so a widely-shared link costs one render, not one per crawl. You can also add "hosted": true to any normal render to get a CDN-backed { url, expiresAt } back instead of the image. Available on every plan, including Free.
09Can I extract clean Markdown from a page for RAG or LLM agents?
Yes. POST a URL to /v1/extract and Rendex returns reader-mode Markdown, JSON, or article HTML pulled from the fully-rendered page — so it works on JavaScript-heavy single-page apps, not just static HTML. It's the fastest way to feed an LLM clean text instead of raw markup. Want the screenshot and the extracted text in one call? Set "extract": true on /v1/screenshot/json. Extraction is available on every plan, including Free.
10Can Rendex monitor a regulatory or policy page for changes?
Yes — this is a core Rendex Watch use case. Watch re-renders any public URL on a schedule (a regulation, policy, pricing, or terms page) and alerts you when it changes — a real-Chrome before/after visual diff with a highlighted overlay, a full-page text diff, or both (the default, so it catches any change out of the box). Every alert leads with a crop of exactly what changed plus a plain-English summary of what and where — on every plan — delivered by email (every plan) or a signed webhook (Starter and up). Create and manage watches in the dashboard or over the /v1/watches REST API, with native tools in MCP, n8n, and Zapier — all on the same API key and credit pool as your renders. More at /watch.
11Is there an MCP server for AI agents?
Yes. Rendex ships with a Model Context Protocol (MCP) server that works with Claude, ChatGPT, Cursor, Windsurf, and any MCP-compatible client. AI agents can capture screenshots as a native tool — no REST integration needed.
12How do I use Rendex in an n8n workflow?
Install the official Rendex community node (n8n-nodes-rendex) from Settings → Community Nodes, add a Rendex node, and authenticate with your API key. Set the Screenshot resource to Capture, choose HTML or URL as the source, and the rendered image or PDF lands in the node's binary output — ready to pipe into S3, email, or any other node. Full guide at /docs/n8n.
13Can I render HTML to an image in Make.com?
Yes. Make doesn't have a native Rendex app, but its built-in HTTP module is all you need. POST your HTML to https://api.rendex.dev/v1/screenshot with an Authorization Bearer header, and Rendex returns the rendered PNG, JPEG, WebP, or PDF for any downstream module. Step-by-step at /docs/make.
14Does Rendex work with Zapier?
Yes. The native Rendex app for Zapier connects to 7,000+ apps with no code — search 'Rendex' in the Zapier app directory, paste your API key, and add a Capture Screenshot or Generate PDF action to any Zap. See /docs/zapier.
15Can I generate invoices or OG images from a no-code automation?
Yes. Send your HTML template to Rendex from n8n, Make, or Zapier and it renders straight to PNG, JPEG, WebP, or PDF — no hosted page required. It's a common pattern for invoices, social cards, certificates, and email previews, with the result attached, uploaded, or emailed in the next automation step.
16How does batch processing work?
Submit up to 500 URLs in a single POST request to /v1/screenshot/batch. Each URL is processed in parallel with shared default parameters and optional per-URL overrides. You can poll batch status or set a webhook URL to receive a callback when the entire batch completes.
17Do you support webhooks?
Yes. Set a webhook URL on any async job or batch request and receive an HMAC-SHA256 signed callback on completion or failure. Webhook payloads include the job result URL, metadata, and a delivery ID for idempotency. Delivery retries with exponential backoff up to 3 attempts.
18How fast are screenshots?
Most screenshots complete in under 3 seconds, with simple pages often under 1 second. The API runs on Cloudflare's edge network across 300+ locations, so requests are processed close to both you and the target website.
19Can I capture full-page screenshots?
Yes. Set "fullPage": true in your request and the API automatically scrolls the entire page, capturing everything including below-the-fold content. Custom viewport dimensions from 320px to 3840px and retina up to 3x are supported.
20Can I capture a specific part of a page?
Yes. Use the "selector" parameter with any CSS selector to capture a specific element — a hero section, pricing table, navigation bar, or any component. For example, "selector": ".pricing-card" captures just that element. You can also use "waitForSelector" to wait for dynamic content to render before capturing.
21Do you support dark mode captures?
Yes. Set "darkMode": true and the API emulates the prefers-color-scheme: dark media query, so websites that support dark mode will render in their dark theme.
22Can I capture pages from different countries?
Yes. Pro and Enterprise plans include geo-targeted capture from 50+ countries. Set the "geo" parameter to any ISO country code (e.g., "US", "DE", "JP") and optionally refine by state and city. The page renders exactly as a local user would see it — localized pricing, language, and ads included.
23What image formats are supported?
PNG, JPEG, WebP, and PDF. You can control the output quality for JPEG and WebP (1-100) and choose the format that best fits your use case. PNG for pixel-perfect screenshots, JPEG for smaller file sizes, WebP for the best of both, and PDF for documents and archival.
24Do you have official SDKs?
Yes. We ship official TypeScript and Python SDKs with full type safety and zero external dependencies. Install with "npm i @copperline/rendex" or "pip install rendex". Both return typed responses — you get your first screenshot in 3 lines of code.
25Where is the API deployed?
Rendex is deployed across 300+ edge locations worldwide. There are no cold starts — every request gets immediate processing on the nearest edge node.
26What happens if I exceed my plan limit?
Your bill stays predictable. Every plan has a hard monthly cap, so you'll never get a surprise charge for overage. Once you hit your cap, requests return HTTP 429 until your next billing cycle. To resume immediately you can either upgrade in one click (upgrades take effect right away) or buy a one-time credit pack — 500 renders for $5 (with lower-priced regional packs from $2 in some countries), no subscription — to keep going without changing plans.
27Can I buy more renders without upgrading?
Yes. Credit packs are one-time top-ups — 500 renders for $5, no subscription (regional pricing applies, with smaller packs from $2 in some countries). They work on any plan including Free, and the credits never expire. Your monthly plan renders are always used first, so a pack only starts drawing down once you've used your included renders. Buy anytime from your dashboard.
28Do free renders have a watermark?
Yes — output on the free tier carries a "rendex.dev" watermark tiled across PNG/JPEG/WebP images (your content stays readable underneath) and a footer line on PDFs. Every paid plan — starting with Basic ($12/month) — is fully watermark-free. Text extraction is never marked. The mark is rendered into the pixels/PDF server-side, so it can't be stripped in code.
29Is my data safe with Rendex?
Yes. Rendex does not store screenshots or rendered content beyond the time needed to deliver your response. Async job results are stored temporarily in encrypted storage and automatically expire. All API communication is over HTTPS. S3 credentials for custom storage are encrypted with AES-256-GCM at rest.
30Do you scan URLs for malware before rendering?
Yes. Every URL is checked against Google Safe Browsing before rendering. If a URL is flagged as malicious — phishing, malware, or social engineering — the request is rejected with a clear error. This protects your infrastructure and end users from rendering dangerous content.
31Can the API access internal or private URLs?
No. Rendex blocks requests to private IP ranges (10.x, 172.16.x, 192.168.x), localhost, link-local addresses, and cloud metadata endpoints (169.254.169.254) — and it resolves each hostname first, so a public-looking domain can't be pointed at an internal address either. URLs that resolve to those ranges are rejected before any render happens.
32Are you GDPR-compliant, and can I get a DPA?
Yes. On a standard synchronous render, the HTML, URL, or Markdown you send is processed transiently and isn't retained after we deliver your response. If you opt into an asynchronous job, batch, or hosted output, the submitted capture parameters are stored only as long as the job needs them — credentials, cookies, and request headers are redacted at the edge before storage, and the params are nulled within 90 days — while the rendered output sits in encrypted storage that automatically expires. We offer a standard Data Processing Agreement (DPA) under the GDPR and UK GDPR on request; email legal@rendex.dev. Our sub-processors are listed in the Privacy Policy, and rendering runs on Cloudflare's global edge.
33Do you provide a VAT-compliant invoice for my business?
Yes. We collect your business or VAT tax ID at checkout, so it's recorded on the Stripe invoice your finance team can expense — EU B2B reverse-charge included. Billing runs through Stripe, and you can switch between monthly and annual billing anytime from your dashboard.
Ship a render in 30 seconds
Grab a key. Paste this. You're rendering.
Free tier is a real tier — same engine, same edge, same MCP, at 3 requests/min. Turn up the throughput when you outgrow it — Basic is 3× faster — not before.
your terminal
curl "https://api.rendex.dev/v1/screenshot" \
-H "Authorization: Bearer $RENDEX_KEY" \
-H "Content-Type: application/json" \
-d '{"html":"<h1>Hello</h1>"}' \
-o out.pngPOST · /v1/screenshot≈ 200 ms
PNG.png@2x retina · transparent · sRGB
JPEG.jpgquality 1–100 · progressive · 4:2:0
PDF.pdfA4 / Letter / custom · outline · margins
WebP.webplossy or lossless · animated supported