Technical model
How JadePDF handles a document
Static application delivery, local document processing, and explicit capability boundaries.
Verified tool flow
Select
The browser receives a local file handle.
Read
Bundled JavaScript reads bytes into browser memory.
Transform
The selected operation runs on the device.
Download
The browser creates a local result for download.
The 18 verified launch tools do not send document bytes to a JadePDF processing endpoint. Ordinary requests for site assets still go to Cloudflare because the browser must load the application itself.
What Cloudflare receives
- • Requests for HTML, JavaScript, styles, images, the manifest, robots file, and sitemap.
- • Standard connection and security metadata needed to deliver and protect those assets.
- • No intentional PDF upload from the verified tool workflows.
What the device handles
- • Selected PDF and image bytes.
- • Page parsing, rendering, reordering, drawing, and output generation.
- • Blob URLs and downloads created for the current browser session.
Capability states
Verified: implemented browser workflow, automated tests, and permission to appear in the sitemap.
Partial: an implementation exists, but a documented limitation keeps the route out of search.
Unavailable: no active processing control is presented.
Verify the behavior
- 1. Open a verified tool such as Merge PDF.
- 2. Open the browser developer tools and clear the Network panel.
- 3. Select local files and complete the operation.
- 4. Inspect requests. Application assets may load, but the PDF should not appear as an outbound request body.
Reproducible examples for three verified workflows
You can generate non-personal test files inside Merge, Split, and Images to PDF. The files, operation, and downloaded result stay in the current browser session. Inspect the output yourself; these examples do not certify arbitrary documents or every PDF feature.