Back to PageivoTesting methodology

How we test Pageivo

A useful PDF tool must do more than produce a download. We check the operation, the output and the privacy assumptions behind it.

1. Function tests

Each tool is tested with small synthetic PDFs created for the specific operation. We verify expected page counts, ordering, extraction ranges, metadata changes, watermark placement, image conversion and encryption behavior where applicable.

2. Output review

We open the generated result instead of treating a successful download as proof of success. For page-copy operations we compare page count and order. For rasterizing operations we inspect small text and image clarity. For encryption we verify that the output requires the intended password in a compatible reader.

3. Privacy model

Pageivo is designed around browser-local document processing. The tool code reads selected files into browser memory and produces the result on the device. We keep analytics and advertising configuration separate from the file-processing path and do not intentionally send selected PDF or image contents to a Pageivo conversion server.

4. Limit tests

Browser tools depend on the user's device. We test representative multi-page and image-heavy documents, but we do not publish a fake universal maximum file size because available memory differs greatly between phones, tablets and desktops.

5. Documentation review

Tool pages and guides are reviewed when behavior changes. We state material limitations, including when compression rasterizes pages, when interactive PDF features may not survive a rebuild, and when a privacy action such as metadata removal is not equivalent to complete document sanitization.