Published October 3, 2026 · 4 min read
PDF Candy documents server-side processing and a deletion window, while a browser-local tool can avoid a file-processing upload for supported tasks. Compare the exact feature, current policy, observed network behavior, output quality, and the risks of the surrounding page.
Scope and decision boundary
Local processing can remove one file-transfer step, but it does not secure a compromised device, browser extension, analytics script, downloaded output, backup, or later delivery channel.
What PDF Candy documents
PDF Candy's security page currently describes server-side processing and says files are deleted within two hours. That replaces the inherited five-hour retention claim. Link the official page and add a checked date because retention language can change.
A browser Network capture can observe the upload used by a tested feature. It cannot verify that server copies, derivatives, logs, or backups are deleted on schedule; that remains a provider-policy and contractual question.
Do not compare unlike feature sets
PDF Candy offers conversions and specialized operations that a narrow local toolkit may not provide, including PDF/A-related workflows. LoveMyFile's potential advantage is the data path for supported browser-local tasks, not a claim to match every feature or output.
- Match the same task, input file, account state, and free or paid tier.
- Check page and file caps, batch behavior, output quality, forms, links, fonts, signatures, metadata, and accessibility.
- Record the official retention statement separately from observed network traffic.
- Use ‘no processing upload observed’ only when the current LoveMyFile build has been tested with synthetic data.
Decision rule
Use PDF Candy when its feature set and documented server workflow fit the task. Use a verified local tool when the operation is supported, the device is trusted, and avoiding a processing upload has material value. Use specialist software when standards compliance, OCR, high-fidelity conversion, support, or managed audit evidence is required.
Publication evidence
Before publication, test at least one simple and one complex sample in both tools, capture the date and settings, and replace broad winners with task-level results. Do not infer security, compliance, or output equality from the absence of an account requirement.
Sources and verification
Primary sources below were reviewed for this revision on September 1, 2026. Requirements, prices, limits, interfaces, and policies can change; open the source again before acting on a high-stakes or time-sensitive task.
- PDF Candy security and data protection — States the service's current server-processing and two-hour deletion policy.
- PDF Candy PDF/A tool — Demonstrates capabilities that a narrow browser-local toolkit may not provide and should not claim to replace.
- Chrome DevTools Network reference — Documents how to inspect requests, payloads, transferred bytes, and request destinations.
- MDN: FileReader — Explains that browser code can read files the user explicitly selects; selection alone does not prove an upload.
- W3C: WebAssembly Core security considerations — States that WebAssembly has no ambient access and must use capabilities supplied by its host environment.
Verification checklist
- Use a synthetic file with a unique marker—not a real sensitive document—for the network test.
- Clear the Network log, process the file, and inspect fetch, XHR, document, beacon, and WebSocket traffic.
- Record browser, version, URL, date, requests, payloads, and limitations; retest after material updates.
Where LoveMyFile fits
Use the LoveMyFile PDF merger for the bounded task described here. Keep any authoritative source or original when applicable, verify the output, and use the official destination or an approved specialist system when the task exceeds that boundary.
This article provides technical and editorial guidance, not legal, medical, tax, immigration, or compliance advice.
