How we write and check our PDF guides

SandboxPDF's guides explain practical document operations and how to inspect their results. They are maintained with the application source so that a change to a tool can also change its instructions. This page describes our approach; it is not an independent certification or a promise that every document has been tested.

Prefer something a reader can verify

A useful explanation gives a concrete input, the relevant settings and an observable result. Our public examples include synthetic source PDFs, saved outputs and measurements. The files contain fictional data and are intended for anyone to reproduce. We do not publish a user's private PDF merely because it was useful in a development test.

We distinguish a tool completing an operation from its result being correct. Page count, page appearance, extracted text, cell placement, metadata and signatures are different properties. A successful download proves only that a file was produced. A passing example is evidence for that input and those settings; it is not proof of universal conversion accuracy.

Separate observations from recommendations

Measured examples name their settings and review date. Advice such as preserving an original or checking an OCR total explains the reason behind the recommendation. Where a format or policy has an authoritative reference, we link readers to that source rather than presenting our guide as the standard itself.

PDF structure and browser behaviour can limit the result. We describe those limitations near the operation they affect. For example, metadata cleanup does not erase printed names, visual signatures do not establish certificate trust, and displayed spreadsheet totals do not restore formulas. We do not describe uncertainty as a successful validation.

Authorship and corrections

The guides are published by the SandboxPDF project. We do not invent named experts, professional qualifications, independent endorsements or testing on devices we have not checked. Editorial review can include automation, but the decision to publish and the accuracy of the claims remain the project's responsibility.

When an instruction becomes outdated, it should be corrected alongside the feature and the affected guide's review date should change. We do not update every article's date just because the site was rebuilt. Readers can report an inaccurate explanation through Contact with the page title, the statement and the observed result. Please leave confidential document contents out of that description.

Use guidance with the right level of confidence

These guides are practical help, not legal advice, financial validation, archival certification or a replacement for an organisation's required review. A receiving archive may require an independent PDF/A validator; a signed document may require trust-chain and revocation checks. For those decisions, use the required procedure and preserve the original file.

The tools and articles are available without payment or an account. Advertising does not change what a PDF transformation can safely claim to do. Read the privacy policy for the difference between local document processing and website or advertising requests.