Privacy, Limitations, and Troubleshooting
Papercraft is designed as a browser-based PDF toolkit centered on client-side document processing. This guide covers the application's stated privacy approach, technical dependencies, and common troubleshooting considerations.
Privacy Commitment
Papercraft's About section states:
100% client-side. No tracking, no uploads.
The application is designed to process PDF documents within the user's browser.
This approach differs from tools that require uploading documents to a remote document-processing server.
How Local Processing Works
The supplied application uses JavaScript and PDF libraries to support browser-side document operations.
Its HTML loads:
| Library | Version | General Purpose |
|---|---|---|
| pdf-lib | 1.17.1 | PDF manipulation |
| PDF.js | 3.4.120 | PDF rendering |
These dependencies are retrieved from a CDN in the supplied HTML.
Client-Side Processing
In a client-side processing model, a selected PDF can be read and manipulated in browser memory.
Generated documents can then be prepared for local download.
The application does not require a server-side PDF conversion endpoint in the supplied router.
Important Distinction
Client-side document processing does not mean the browser makes no network requests.
Papercraft's HTML includes external library resources and advertising integrations.
Those resources may involve network communication independently of the document-processing operations.
The supplied files do not establish that PDF contents are transmitted to those services.
Privacy and Advertising
The supplied HTML includes OK Ads integration.
Advertising resources and the application's PDF processing functionality are separate components.
The site's stated privacy commitment should be distinguished from the data-handling policies of any external resources loaded by the webpage.
Content Security Policy
The supplied HTML includes a Content Security Policy configuration.
It restricts selected resource types and allows specified resources needed by the application.
The policy includes restrictions for:
- Scripts
- Styles
- Images
- Network connections
- Workers
- Frames
- Embedded objects
- Form destinations
Implementation Consideration
The policy uses a fixed script nonce in the supplied HTML.
For a stronger nonce-based security model, cryptographically unpredictable nonces should normally be generated for individual HTTP responses.
The effectiveness of the policy also depends on deployed response headers and the behavior of loaded resources.
Technical Requirements
Papercraft requires:
- A modern browser
- JavaScript enabled
- Working PDF dependencies
- Sufficient available memory
- Support for the browser features used by the selected PDF tool
Browser Compatibility
Actual compatibility depends on the implemented Viewer and Watermark modules.
Some browsers may handle PDF workers, downloads, or large documents differently.
Troubleshooting
The Application Does Not Load
Check that:
- JavaScript is enabled.
- Application scripts load successfully.
- The browser supports the required JavaScript features.
- Network restrictions are not blocking dependencies.
The Viewer Is Blank
Possible causes include:
- Invalid PDF input
- PDF parsing failure
- Missing PDF.js resources
- Worker loading problems
- Browser rendering limitations
PDF Rendering Is Slow
Large PDFs, high-resolution images, or complex vector graphics can require significant browser memory and CPU resources.
Try a smaller document if necessary.
The Watermark Does Not Appear
Check the selected watermark content and configuration.
Review opacity and page selection settings where available.
The Result Does Not Preserve Expected Appearance
PDF documents may contain specialized fonts, transparency effects, or complex graphics.
Inspect the generated output before distribution.
A Navigation Tab Shows a Placeholder
The selected tool may not yet be implemented.
In the supplied version, Merge, Organize, Split, Extract, Redact, Compare, and Scrub are placeholder routes.
A Download Does Not Start
Browser download policies or other restrictions may interfere with generated file downloads.
Check browser permissions and retry.
Theme Controls Do Not Work
The application HTML contains a theme toggle, but its exact behavior depends on the associated JavaScript and stylesheet implementation.
Check that all required scripts load.
Known Limitations
| Area | Limitation |
|---|---|
| Viewer | Rendering behavior depends on PDF.js and the Viewer module |
| Watermark | Detailed defaults and output behavior depend on the Watermark module |
| Merge | Placeholder |
| Organize | Placeholder |
| Split | Placeholder |
| Extract | Placeholder |
| Redact | Placeholder |
| Compare | Placeholder |
| Scrub | Placeholder |
| Large PDFs | Subject to browser memory and processing constraints |
| External Dependencies | CDN resources must be available where required |
| Document Security | Watermarks do not provide encryption or secure redaction |
Recommended Practices
- Keep backup copies of original documents.
- Review modified PDFs before sharing them.
- Confirm that documents remain readable.
- Use suitable tools for sensitive document sanitization.
- Avoid treating watermarks as access controls.
- Check whether a feature is available before relying on it.
Reporting Issues
When reporting a Papercraft problem, include:
- The selected tool
- Browser and operating system
- Approximate PDF size and page count
- Relevant error message
- Steps needed to reproduce the issue
Avoid sharing confidential document contents unless appropriate.
Final Reminder
Papercraft is designed to make everyday PDF operations more accessible through the browser.
Its current supplied architecture establishes a foundation for document viewing and watermarking, with additional PDF tools represented as future modules.
Always verify resulting documents before using them in important workflows.
Updated 8 days ago