Doppio alternative
Start with the part that matters most and is least flattering: Doppio's free tier is bigger than ours. From doppio.sh/pricing, checked 2026-08-08, their Basic plan is free with 400 documents a month, no card and no time limit. Renderpaper's free tier is 50.
If a generous free allowance is what you are optimising for, that is the answer and the rest of this page will not change it.
The honest table
Competitor figures from doppio.sh/pricing, checked 2026-08-08.
| Renderpaper | Doppio | |
|---|---|---|
| Free tier | 50 documents/month | 400 documents/month |
| Entry paid | $19/month, 3,000 documents | $16/month, 4,000 documents |
| Next tier | $59, 15,000 documents | $48/month, 12,000 documents |
| Overage | $4 per 1,000 | $0.0037 per document on Pro ($3.70 per 1,000) |
| Stored templates, render by id with data only | Yes | Not the primary model |
| Browser editor for non-engineers | Yes | No |
| Screenshots as well as PDFs | Images: PNG, JPEG, WebP | Yes |
| Ungated trial with no account | Yes — /try |
No |
| Headers/footers as an option | No | Documented options |
On raw volume per dollar, Doppio is competitive at every tier and better at the bottom. Say so plainly rather than build a table that hides it.
When to use Doppio instead
You want the largest free tier. 400/month is enough to run a small production workload for nothing.
Screenshots are a first-class need. Their product covers page capture as a peer feature, not an adjacent one.
Volume is the whole decision. Their per-document cost at the paid tiers is lower.
When Renderpaper fits better
There is one reason, and it is not price.
The document lives outside your codebase. Renderpaper stores the template and gives it an editor, so the person who owns the design — a designer, an ops lead, whoever actually decides where the logo goes — changes it without a deploy. Your code sends JSON and keeps sending the same JSON.
If your documents are built and maintained entirely by engineers, that mechanism is overhead and Doppio's better volume pricing should win.
Migrating from Doppio
Both accept HTML and return a PDF, so a like-for-like swap is an endpoint and a header. Moving the document into a stored template is the optional second step, and the one that buys the difference above.
You can also upload an existing rendered PDF and get an editable template back, rather than reconstructing it by hand.
Try it
https://renderpaper.com/try — no account, no email.
Checked against doppio.sh on 2026-08-08.