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.
Add a recipient-and-purpose watermark to 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.
—
Short and specific works best: who receives it and why.
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.
A restricted-use copy should state who may receive it and why. This makes reuse for another transaction visibly inconsistent.
No. Pages are flattened into protected pixels before PDF export. The watermark is not stored as a separate editable text layer.