HTML to PDF - Chromium render (private, no retention)
Pricing
$150.00 / 1,000 results
HTML to PDF - Chromium render (private, no retention)
Render HTML to PDF with a real Chromium print engine - modern CSS, web fonts and SVG come out as a browser prints them. Paste HTML inline (invoices, reports) or pass a file URL. Privacy-first: inputs deleted at conversion end, outputs within an hour, failed runs never charge.
Pricing
$150.00 / 1,000 results
Rating
0.0
(0)
Developer
Nir Diamant
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
HTML to PDF - real Chromium render (private, no file retention)
Renders HTML to PDF with a real Chromium print engine, so modern CSS, web fonts, flexbox/grid layouts, and inline SVG come out the way a browser prints them - not the way a word processor guesses them. Paste HTML straight into the input (the generated-invoice case: no hosting step, no temp bucket) or point it at an .html file URL.
Why this one
- Chromium, not a converter library. The render path is a headless Chromium print, the same engine your users' browsers use. CSS that renders in Chrome renders here.
- Inline HTML input. Most HTML-to-PDF jobs start from generated markup
(invoices, reports, tickets). Paste it directly as the
htmlinput; no need to host the file anywhere first. - No file retention. The input is deleted the moment the conversion finishes. The output is kept for about an hour, then deleted. Your documents are not stored, mined, or used for anything.
- Failed runs never charge. One dataset item per successful conversion; a failure produces no item and no charge.
Input
Either of:
html(string): the HTML to render, passed inline.fileUrl(string): direct http(s) URL of an .html file, up to 50 MB.fileName(optional): base name for the output file.maxWaitSeconds(optional): how long to wait before failing, default 300.
Output
- The PDF is stored as the
OUTPUTrecord of the run's key-value store (the dataset row carries its directoutputUrl). - One dataset row per successful conversion:
pair,fileName,outputFileName,inputBytes,outputBytes,durationSeconds,outputUrl.
Honesty block
- The conversion runs on hushvert's server lane (Gotenberg's Chromium route), not inside this actor. Retention: inputs deleted at conversion end, outputs auto-deleted after about an hour.
- Self-contained HTML (styles and images inlined, e.g. data: URIs) is the reliable input: it renders identically every time. External assets referenced by URL may or may not be reachable from the sandboxed render engine; do not depend on them.
- Limit: 50 MB per file.
Who runs it
Built by the hushvert founder. The browser-side conversion engine is MIT open
source (@hushvert/engine on npm); formats a browser can convert (images, HEIC,
audio, archives, PDF page ops) are free and client-side at
https://hushvert.com and are deliberately not sold here. Developer API docs:
https://hushvert.com/for-developers
