How the browser workflow is tested
The browser tool uses PDF.js for PDF rendering and pdf-lib for output generation. Test runs use non-confidential PDFs with text pages, scanned pages, tables, mixed page sizes and rotated pages. The core checks cover choosing a file, rendering, page navigation, stamp placement, export and reopening the generated PDF.
For the ordinary browser workflow, PDF files and stamp images are handled by browser-side code rather than sent to a PDF conversion server. This is a practical privacy design, not a claim of absolute security or an independent security certification. Use an offline workflow whenever your organisation requires one.
Browser and file support
The target environment is the current stable release of Chrome, Microsoft Edge, Firefox or Safari. Keep the browser updated. Performance depends on available memory, device hardware and PDF complexity.
The browser tool accepts PDF files and PNG or JPEG stamp images. Typical unencrypted PDFs are the intended workflow. Scanned PDFs can be processed as rendered pages, but the tool does not perform OCR or edit the document text. Password-protected, damaged or unusually large PDFs may need to be opened or handled locally before use.
How content is reviewed
Guides are checked for a clear workflow, realistic limitations, links to the relevant tool or manual, and wording that does not present visible stamps as legal proof. Screenshots and technical descriptions are reviewed again when the related workflow changes.
Articles provide practical information, not legal, compliance or security advice. If you find an error, use the Contact page so it can be reviewed and corrected.
Updates and change record
Meaningful browser-tool changes are checked against the core workflow above. Documentation changes are reflected in the relevant manual or article, and each article shows its publication or update date. The Windows desktop app exposes its version and update availability inside the application.
For a current feature description, use the User Manual. For corrections, privacy questions or feedback, use the Contact page.