Last updated: June 29, 2026
Status and Known Limits
This page summarizes the current public workflow status and known limitations for JUST FREE PDF. It is intended to help users decide whether the editor is appropriate for an ordinary document, a portal submission, or a file that needs a stricter workflow.
Current workflow status
| Workflow | Status | Notes |
|---|---|---|
| Open PDF | Supported | Works best with standard PDFs on a trusted device and modern browser. |
| Edit source text | Limited support | Best for small changes in PDFs with real text objects and usable font information. |
| Fill forms | Supported with review | AcroForm, flat form, scan, and XFA behavior can differ; reopen exports before submission. |
| Visual signature | Supported | A visible mark is not a certified digital signature or notarized workflow. |
| Organize pages | Supported | Review final page count, page order, and attachments before sharing. |
| OCR | Limited / not guaranteed | Scanned PDFs need caution; OCR may help search but may not recreate source text. |
| Redaction | Not a certified redaction workflow | Do not rely on visual cover-ups for sensitive information. |
Known limits
- Scanned PDFs may need OCR or annotation instead of direct text editing.
- XFA forms may not behave like standard AcroForm fields in a browser workflow.
- Font-subset PDFs may not support every replacement character or spacing pattern.
- Long text replacements may change line wrapping, lists, tables, or column alignment.
- Visual signatures are not certified digital signatures and do not provide identity verification by themselves.
- Redaction should use a real redaction workflow, not a white rectangle, black box, or other visual cover-up.
- Protected, encrypted, permission-restricted, or regulated documents may require an approved workflow.
- Mobile viewers and portal previews may render a completed PDF differently from the editor screen.
Data handling status
JUST FREE PDF is privacy-conscious and server-assisted where needed. Some workflows may use server processing for upload intake, document analysis, operation history, export generation, and download delivery. Uploaded PDF contents should not be used for advertising targeting, analytics events, resale, or AI training. Users should avoid uploading highly sensitive legal, medical, tax, financial, identity, school, employment, or regulated documents unless they understand and accept the workflow boundary.
Advertising status
The site may include Google AdSense account verification and ads.txt configuration. During review, public pages should not include premature ad slots near upload, edit, export, or download controls. Users should never be asked to click ads to support the site.
What to test after each deployment
- Open the homepage and confirm the current privacy wording is visible.
- Upload a harmless sample PDF, make one small edit, export, and download the result.
- Open the exported file in another viewer and check text, form fields, signatures, and page order.
- Verify sitemap, robots.txt, ads.txt, and webmanifest response headers.
- Confirm public pages do not load Google Analytics or Google Tag scripts during the review period.
Current production checks
| Check | Expected result | Why it matters |
|---|---|---|
| Homepage versioned assets | /app.20260629-production-006.js and /app.20260629-production-006.css | Confirms users and crawlers receive the current bundle without relying on stale fixed-path caches. |
| Editor bundle wording | No public preview, fallback, stage, or internal startup labels | Supports a stable production impression. |
| Cookie status | No Google Analytics or Google Tag Manager during review preparation | Keeps policy wording aligned with code. |
| Ad placement | No ad units near upload, edit, export, or download controls | Reduces accidental-click and quality risks. |
Related pages
- Sample PDF test files and workflows
- Data flow and privacy boundaries
- Changelog
- Browser PDF editor security
Manual editor smoke test
After deployment, test the editor with harmless sample files rather than private documents. Use one selectable text PDF, one image-based scan, one flat form, and one simple form with visible fields. Confirm upload, page rendering, one small edit, export, download, and second-viewer review. Record any difference between the editor screen and exported file so the status page can reflect real behavior.
Production response checks
Source changes only matter after the deployed site serves them. Confirm that the homepage, guide pages, sitemap, robots.txt, ads.txt, webmanifest, CSS, JavaScript, and vendor assets return the expected status codes, content types, and cache-control headers. If production still serves an old binary or static bundle, AdSense and Search Console will evaluate the old site.