Step 1
Load the static application
Cloudflare Pages serves HTML, CSS, JavaScript, images, and the bundled PDF worker. No account or document-processing session is created.
Technical walkthrough
The verified launch tools use a static application and the user's browser. This page describes the actual processing boundary, not an aspirational backend.
Cloudflare Pages
└─ serves static JadePDF assets
↓
User browser
├─ receives a local File object
├─ reads PDF/image bytes into memory
├─ runs the verified transformation
└─ creates a local Blob downloadStep 1
Cloudflare Pages serves HTML, CSS, JavaScript, images, and the bundled PDF worker. No account or document-processing session is created.
Step 2
The browser provides a File object after you choose or drop a PDF or image. The verified workflow reads those bytes into local browser memory.
Step 3
Bundled JavaScript uses pdf-lib or PDF.js to inspect pages, copy objects, draw text, embed images, or assemble a new document.
Step 4
The tool creates a Blob or ArrayBuffer for the output and gives the browser a temporary local download URL.
| Layer | Implementation | Boundary |
|---|---|---|
| Site | Astro 7 with React islands | Static assets from Cloudflare Pages |
| PDF manipulation | Bundled pdf-lib 1.17.1 | Browser memory |
| PDF parsing and previews | Bundled PDF.js 6.2.108 module worker | Same-origin worker; scripting and XFA disabled |
| Document storage | None operated by JadePDF for the launch tools | Local selection and download |
Open the browser Network panel, merge two non-sensitive test files, and inspect the requests yourself.