Visual PDF generation for developers. Create templates. Inject JSON. Generate documents instantly. Contracts, invoices, reports & more. JSON in → PDF out. ⚡
Belgium
- Tweets 23
- Following 36
- Followers 5
- Likes 0
Want to see Generatr in action? We just published a full product demo on YouTube 🎥
Watch how templates, JSON, and the API come together to generate dynamic PDFs at scale — no HTML/CSS required.
piped.video/0d8LRmiQObg
#saas #devtools
1
12
We built Generatr with one rule: everything you need to generate documents at scale, nothing superfluous.
Here's what that looks like 🧵
1
1
5
Native multi-language. One template, every market.
Translate your document into as many languages as you need. Pass ?lang=fr at API call time and you're done. One template. No drift. Always.
1
1
Folders, multi-org, reusable partials.
Organise templates in a tree. Isolate clients in separate orgs with role-based access. Write your header once as a partial, reuse everywhere — one edit propagates instantly.
generatr.app/?utm_source=twi…
Hot take: template-as-code is a trap.
'Just write HTML/CSS templates' sounds fine until:
• Your legal team needs to tweak a clause
• Your ops team needs a new report format
• Every change requires a PR + deploy
We chose a visual editor for Generatr. Here's why 🧵
1
1
2. No rendering surprises.
HTML/CSS in Puppeteer is a minefield. Flexbox bugs. Font rendering differences. Page break orphans.
A structured JSON tree + dedicated layout engine = predictable output. Every single time.
1
3. Instant live preview.
Paste your JSON test data → see the exact rendered document, paginated, in real time. No 'push to staging → generate → debug → repeat' cycle.
generatr.app/?utm_source=twi…
How does Generatr turn a visual template into a PDF in under 200ms?
No black magic. Just a clean pipeline. Let's break it down 🧵
1
1
Step 3 — Layout engine handles pagination.
This is the hard part. We calculate line heights, table row breaks, image dimensions — and split pages accordingly.
Headers, footers, page numbers — all positioned correctly. A4 or Letter. Every time.
1
Step 4 — Render & stream.
Resolved document → PDF rendered server-side → binary streamed back.
That's it. One POST. JSON in, PDF out.
No Puppeteer. No wkhtmltopdf. No 'it works on my machine.'
generatr.app/?utm_source=twi…
Step 2 — Templating engine resolves your data.
Variables, loops, conditionals — your template comes alive with real data.
We parse the JSON tree, inject your data, and produce a resolved document — all server-side, no browser needed.
1
Step 3 — Render & stream.
Resolved document → PDF rendered server-side → binary streamed back.
That's it. One POST. JSON in, PDF out.
No Puppeteer. No wkhtmltopdf. No "it works on my machine."
generatr.app/?utm_source=twi…
Document generation at scale is still broken in 2026.
Most teams are stuck with:
• Hand-coded HTML/CSS templates nobody wants to maintain
• Page breaks that break the second data length changes
• Fragile Puppeteer/headless Chrome pipelines
There's a better way. 🧵
1
1
3
What if generating a PDF was just:
1. Design your template visually (no code)
2. POST your JSON to a single API endpoint
3. Get a production-ready PDF back
Page breaks, headers, footers, pagination — all handled.
One template, any language.
That's what we're building. ↓
1
1
Generatr: visual PDF template builder + dead-simple API.
• WYSIWYG editor — create templates in minutes
• Dynamic templating — loops, conditions, variables
• Live preview with real pagination
• Native multilingual + AI translations
generatr.app/?utm_source=twi…
#buildinpublic
1