From Paperplane to Converterer: rebuilding a file-conversion API for the next decade

Paperplane is now Converterer. Same team, same infrastructure, broader scope. If you’ve been using Paperplane’s HTML-to-PDF API since 2018, your account, keys, and integration keep working at paperplane.app for now. We’ll reach out to migrate you across when we’re ready.

This post is the long answer to the questions we’ve been getting since the rebrand: why, what’s changed, and what you need to do.

Why we rebranded

Paperplane started in 2018 as an HTML-to-PDF service. That was the entire product. You sent us a URL, we sent back a PDF. We ran it on headless Chrome, we wrote about how to do it yourself in our 2019 post on the topic, and we picked up customers who liked the idea of not maintaining a Chrome cluster themselves.

Customers kept asking us for file conversions beyond HTML-to-PDF. MP4 to GIF, DOCX to PDF, HEIC to JPG, format pairs that have nothing to do with HTML or printing. So we built them. The product surface grew well past what “Paperplane” described.

Two practical problems with the old name:

Discoverability and clarity. Someone searching “convert PDF to DOCX in Python” might still find us via SEO, but the name “Paperplane” didn’t tell them we do file conversions across formats. The name described one slice of what the platform actually did.
Positioning. Telling a developer “we’re an HTML-to-PDF API that also does file conversion” is a worse pitch than “we’re a file conversion API.”

So we changed the name. Converterer (yes, three E’s, we know) describes what the platform is in 2026: a file conversion API that handles documents, images, audio, video, and website-to-PDF capture as one product, accessed through one API.

What’s the same (Paperplane keeps running)

Existing Paperplane customers don’t have to lift a finger today. Both platforms continue to run side-by-side:

API endpoints. api.paperplane.app keeps working exactly as it does today. Same hostname, same auth, same request and response shapes.
Authentication. Your existing API keys continue to work on Paperplane. No re-issuance.
The HTML-to-PDF service. Same engine, same options, same output. Now also available as Website Capture on the Converterer side.
Webhooks. Unaffected. Webhooks go out from us to you, so your delivery URLs are unchanged.

What Converterer adds

The pieces that are new on the Converterer platform:

100+ conversion pairs across documents, images, audio, and video. The full matrix is at /matrix/. Some pairs that didn’t exist under Paperplane and now do: PDF → DOCX, MOV → MP4, HEIC → JPG, MP4 → MP3, NUMBERS → CSV, KEY → PPTX, and the long tail of ~300 more.
Two APIs, one billing line. /convert for file conversion, /jobs for website capture. They share rate limits and your monthly quota, no duplicate accounts.
Re-aligned pricing. New tiers are generally cheaper and more competitive than the old Paperplane plans. When we migrate you across, you move to the new pricing automatically. See pricing.
Code samples for every major language. Native HTTP examples for Python, Node.js, PHP, Laravel, Ruby, Go, Java, plus plain cURL. Real, runnable, idiomatic code per language. Browse the developer docs.
Format hubs. Each format has a hub page with all the conversions in and out, plus the API paths. Useful when you’re scoping which conversions you might need across a workflow.
Refreshed everything. New marketing site, new docs, new dashboard. Same battle-tested API backend you were using before.

How the migration works

When we’re ready to move you to Converterer, the migration is a quick, walked-through swap. We’ll reach out to each existing customer personally, in order.

New account on the Converterer dashboard at dashboard.converterer.com. We set this up alongside your existing Paperplane account.
API keys transferred from Paperplane to Converterer. You don’t need to re-issue anything.
Hostname switch from api.paperplane.app to api.converterer.com in your code or .env. A one-line change.

That’s it. The migration is opt-in for now, and we’ll only ask you to do it once we’ve done the prep on our end. Until then, nothing changes for you.

If anything breaks, or you want to migrate sooner than we reach out, contact us.

What we kept writing about

The old Paperplane blog had two posts that still get referenced regularly:

Print CSS basics in 10 minutes, the practical guide to @media print, page breaks, and the @page rule. Refreshed for 2026 with print-color-adjust, the new headless Chrome behavior, and the parts of the spec that have stabilized in the last few years.
Modern HTML to PDF conversion, what it takes to render HTML to PDF in production, updated for Playwright, Cloudflare Browser Rendering, and the post-2024 serverless landscape.

Both were originally written when Paperplane was just an HTML-to-PDF service. Both are still useful in 2026 if you’re choosing between rolling your own rendering pipeline and calling an API. We’ve kept them updated rather than archived because the underlying questions, should I run my own headless Chrome cluster?, haven’t gone away.

The roadmap, briefly

A few things in flight that we’ll write about as they ship:

More format pairs as customers ask for them.
Webhook reliability work, exactly-once delivery semantics, configurable retry policies.
Improved batch endpoints for high-volume conversion workflows.
Deeper integrations with the no-code platforms.

We’ll keep this blog as a working developer log: occasional notes on what changed in the file-conversion world, what we built and why, and the kinds of “we hit a weird bug, here’s the fix” posts that we’d want to read ourselves.

If there’s something you’d like covered, a specific use case, a comparison, an integration deep-dive, let us know. The blog only works if it’s useful.

TL;DR

Paperplane is now Converterer. Same team, broader product.
Paperplane keeps running for existing customers. Nothing changes today.
We’ll reach out individually to migrate you across to the new platform: new account, key transfer, one-line hostname swap.
New pricing on Converterer is generally cheaper and more competitive than the old Paperplane plans.
The HTML-to-PDF use case is now Website Capture, same engine, clearer name.
The two old blog posts (print CSS, HTML to PDF) are refreshed and stay live.
New scope: documents, images, audio, video, and website capture across one API. See what’s supported.

Thanks for sticking with us through the rename.