Last updated: June 29, 2026
Status and Known Limits
This page describes the current product boundary for JUST FREE PDF. It is intentionally specific: a trustworthy PDF editor should explain what it can do, what it cannot do, and when users should choose a different workflow.
Current supported workflows
- Open ordinary PDFs in the browser interface for review.
- Make small edits to PDFs that contain selectable source text.
- Add typed overlays to flat form areas.
- Add simple visual signatures when the recipient accepts that signature type.
- Reorder ordinary pages and review the final sequence.
- Export a completed PDF and reopen the downloaded copy for inspection.
Current data-handling boundary
JUST FREE PDF is privacy-conscious but not offline-only. Some workflows may use server processing for upload, document analysis, operation history, export generation, and download delivery. Uploaded PDF contents are not intended for advertising targeting, analytics events, resale, or AI training. Users should avoid uploading highly sensitive legal, medical, tax, financial, or regulated documents unless they understand and accept the workflow boundary.
Known limits
| Limit | What it means | Recommended action |
|---|---|---|
| Scanned PDFs | Image-only pages cannot be rewritten as normal text without OCR. | Use OCR, the original source file, or visual overlays with review. |
| Font subsets | Some PDFs contain only the characters used in the original. | Make small edits and inspect spacing after export. |
| XFA forms | Some dynamic forms require a specific desktop viewer or portal. | Follow the official instructions. |
| Certified signatures | A visual signature is not a certificate-backed digital signature. | Use the required signing platform. |
| True redaction | Covering text does not remove underlying content. | Use a specialist redaction workflow. |
Operational status for review
The public site should keep advertising away from upload, editing, export, and download controls. During review, Google Analytics and Google Tag scripts should remain disabled unless the privacy and cookie policies are updated to match. The sitemap should include only canonical, indexable pages. Redirect-only legacy pages should stay out of the sitemap.
Recent reliability focus
- Clearer privacy and server-processing language.
- Expanded practical guides for scans, forms, text shifts, metadata, and redaction.
- Cache-control and manifest content-type improvements in the server code.
- Reduced overlap between tool pages and guide pages.
- Redirects for legacy thin template pages.
When to avoid the tool
Do not use a general online PDF editor when the document requires certified signing, notarization, legal redaction, regulated retention controls, or an official portal workflow that specifies another application. Do not use it as a substitute for legal, compliance, tax, medical, or professional advice. When in doubt, use the original source document or a controlled offline workflow.
Verification checklist after deployment
- Open the homepage and confirm the data-processing notice is visible near upload.
- Open the privacy and cookie policies and confirm they match the active scripts.
- Confirm new guide pages return 200 status codes.
- Confirm the sitemap lists the expanded guide set.
- Confirm static resource caching and webmanifest content type are active in production.
- Submit the sitemap in Search Console and allow time for recrawling before AdSense review.