Plugin processing
PufferPDF converts PDFs in a browser Worker inside the WordPress administration screen using a bundled WebAssembly runtime. It does not send PDF bytes to an external conversion service.
A PDF chosen from your computer is read by the browser and is not uploaded by this workflow. When you select a Media Library PDF, the browser fetches the attachment from the WordPress storage where it already resides; PufferPDF does not create another copy.
What reaches WordPress
Before you approve an action, PufferPDF lets you review the extracted structure, warnings, Markdown, and proposed output. When you preview a publishing plan, create content, or reprocess a draft, the reviewed Gutenberg blocks, title, source identity, conversion options, and bounded inspection metadata are sent to your own WordPress site. PDF bytes are not included.
Previewing a publishing plan writes no posts or pages. Reversible multi-item publishing creates only draft or pending content, and final publishing remains an editorial action in WordPress.
Conversion records
PufferPDF conversion records store source hashes, parser and option metadata, bounded result summaries, and relationships to generated WordPress content. They do not store PDF bytes.
For Media Library files that WordPress can read, the plugin independently computes a SHA-256 hash to detect source changes. Files that cannot be verified remain clearly marked unverified instead of being presented as current.
This marketing website
Pufferpdf.com does not include analytics, advertising pixels, account registration, contact forms, or marketing cookies. The site does not ask you to upload a PDF.
The site is hosted on Vercel. Standard request information may be processed by Vercel to deliver and secure the site under its Privacy Notice.
PDF conversion happens in wp-admin. Reviewed blocks and metadata go to your WordPress site for planning or approved writes. Conversion records contain metadata, not the PDF.