Alternatives
Moving off CraftMyPDF
A hosted editor where templates are composed by placing components — text, images, tables, barcodes — and rendered from JSON over an API, with expression syntax for transforming data and connectors for no-code tools.
Why teams move
- Placing components is a fixed-canvas model. It suits a label, a certificate or a packing slip, and it gets progressively harder as the document's length starts depending on its data.
- Expression syntax carries the complicated cases. Once transformation logic lives inside template expressions, it deserves the same review and test discipline as application code.
- For variable-length designs, validate the rendered output with representative data before relying on it at scale.
Side by side
Three properties that do not change week to week. No price columns and no feature checkmarks — those go stale quietly, and a comparison that misstates the other tool is worse than none.
| CraftMyPDF | pdfs.build | |
|---|---|---|
| What you author | Placed components, with expression syntax for the logic. | A design with a schema, edited in plain English. |
| What decides page breaks | The canvas. | The design states them; the engine composes to them. |
| As the data grows | Determined by the template; validate representative data before rollout. | The ordinary case. Each design records what it does. |
The checkable parts
Claims worth verifying rather than taking on trust — each links to its source, checked September 2026.
-
Templates are authored in a drag-and-drop editor and rendered from JSON; data transformation is expressed with JavaScript-style expressions.
CraftMyPDF ↗
What is different here
Length is the data's decision
Nothing here assumes a canvas of known height. Repeating headers, page-break rules and content that pushes the page count are the starting point rather than the thing that breaks the design.
Editing without placing boxes
Changes are described in plain English to an assistant that edits the template, which scales to a fifty-page handbook in a way dragging elements does not.
Behaviour written down
Each design states what happens under real data, so it can be checked before it is trusted with a customer's document.
When to stay with CraftMyPDF
It is often the right answer. If any of these describe you, this is not a migration worth making.
- Your documents are short and fixed — labels, badges, certificates, single-page slips — where a visual canvas is simply the faster tool.
- Non-technical colleagues own the templates and are productive there. Do not take that away from them.
- The workflow is already wired through Zapier or Make and the connector is doing the real work.
What moving involves
- 1 Fixed-layout templates transfer straightforwardly; move the ones that have started fighting variable-length data first.
- 2 Logic living in template expressions becomes part of the schema or stays in your application, where it can be tested.
- 3 Short fixed-format documents are worth leaving behind — replacing them buys nothing.
The API reference covers authentication, the render call and error handling; the template gallery has designs to start from rather than a blank page.
Other migrations
Render one and compare
Free tier includes 2 templates and 50 watermarked PDF renders per month. No credit card required.
Start building free