Learn how PdfnMore handles request-scoped PDF processing, temporary files, downloads and future explicitly saved documents.
Current production statement · Updated September 2026
A normal conversion or edit request does not silently place the uploaded file or result into a permanent user document library. Results are returned to the browser for download.
Keep your original file until you have opened and verified the result; the current core tools are not intended to be your only document storage location.
Some operations need temporary server files because the underlying document processor works with filesystem paths. Those operations use request-scoped temporary working directories that are removed when the processing request exits.
Other simple operations can process document bytes in memory. PdfnMore does not publish a broad retention-time promise that extends beyond what the production implementation can technically enforce.
My Documents is designed as a separate, authenticated feature. A document should enter that library only after an explicit save choice or a future clearly enabled auto-keep preference.
The planned saved-document entitlements remain 5 documents for Free, 25 for Pro and 100 per Business user. These limits are server-side foundations, not a claim that the public document library is already available.
Trust Center · Privacy · Security · File deletion · Help
No. Current processing does not silently save files, and the future My Documents design requires an explicit save choice unless a user later enables a clear auto-keep preference.
For workflows that use request-scoped temporary working directories, the application removes those directories when the processing request finishes.
A deletion promise should match every production storage path. PdfnMore publishes only retention behavior that the current implementation can support and verify.