Are documents uploaded while they are processed?
No. Files are read into browser memory, processed with Canvas and a local pdf.js worker, then downloaded through a temporary object URL.
Use an automatic date-and-code watermark or write your own for images or PDFs, flatten the result, and place multiple image sides on one A4 page. Files never leave your browser.
One PDF, or up to four JPG, PNG, or WebP images.
Optional: use these fields to build the watermark text for you.
Edit this directly. The last text you use stays on this device.
Protected output
Choose a document and define its permitted use. The finished copy will be flattened so the watermark is not a removable PDF text layer.
Local pipeline
The File API reads bytes directly from your device. No upload endpoint exists in this workflow.
Canvas draws a unique, irregular wave pattern using browser cryptographic randomness.
The protected pixels are exported as PNG or rebuilt into a PDF with no removable watermark text layer.
The tool is designed for identity documents and other sensitive copies. Its processing path stays inside browser memory.
No. Files are read into browser memory, processed with Canvas and a local pdf.js worker, then downloaded through a temporary object URL.
Yes. Select both images and choose ‘Stack on one A4 page’. Each side is watermarked before the A4 sheet is assembled.
No. They are optional helpers for building the watermark text. You can edit that text directly or use an automatic date and unique code.
No. Pages are flattened into protected pixels before PDF export. The watermark is not stored as a separate editable text layer.