| 开发者 | senols |
|---|---|
| 更新时间 | 2026年8月18日 21:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
_pufferpdf_* metadata. Generated posts, pages, revisions, taxonomy terms, and source PDF attachments remain under the site's control.
Learn more about the workflow at pufferpdf.com.
Third-party software
PufferPDF includes a reviewed browser WebAssembly runtime. Third-party attribution, upstream source details, redistribution notices, license texts, provenance checksums, and exact rebuild instructions are consolidated in THIRD_PARTY_NOTICES.txt and the files it references.
pufferpdf folder to /wp-content/plugins/.PufferPDF's conversion requests do not upload PDF bytes. Classification and extraction run in a browser Worker. A Media Library PDF already resides on the user's WordPress storage and is fetched from there for browser processing. Reviewed blocks, titles, source identity, and bounded inspection metadata are sent to the user's own WordPress site only when they create a draft or publication.
Not yet. It detects pages that need OCR and prevents silent imports of fully scanned documents.
The parser extracts native text only. Pages without usable text require a later OCR step, so importing the available text could omit content.
PufferPDF updates only the draft linked by the latest conversion record. It refuses stale records, non-draft targets, source-hash races, and drafts edited since the prior conversion. Identical reruns perform no write.
Paginated inventory avoids hashing many files synchronously, so a converted Media Library row remains unverified until you select it for an exact SHA-256 check. WordPress also cannot independently hash a file that is unavailable on its server filesystem. The browser can still process an offloaded file when the media host permits HTTPS CORS access from wp-admin, but PufferPDF does not label that source current without server verification. Reversible multi-post publishing requires WordPress to verify the Media Library file independently. An offloaded attachment without server-readable bytes can still be downloaded and selected through the independent file-picker workflow.
PufferPDF supports current desktop versions of Chrome, Edge, Firefox, and Safari. Conversion requires Web Workers, WebAssembly, the File API, and SHA-256 support through Web Crypto. If the browser or site context does not provide those capabilities, PufferPDF stops before conversion and explains what is missing.
Deactivation preserves all data. Deleting the plugin removes its hidden conversion records, publication manifests, and private PufferPDF metadata. It does not delete generated posts or pages, their revisions, taxonomy terms, or source PDF attachments.