Named authors, real backgrounds
Every guide carries a byline, and every byline is a person with a stated role and a stated area of responsibility. Their backgrounds are on their author pages. Nobody here is a stock photograph attached to an invented name, which is a low bar that a surprising amount of the internet does not clear.
Who writes what
Each area has one person responsible for it.
| Author | Responsible for |
|---|---|
| The Document Desk | Site-wide guides, tool documentation, anything cross-cutting |
| Ravi Menon | Printing, paper sizes, scanning, page geometry |
| Hannah Whitlock | Revision workflow, reading, accessibility |
| Tomasz Kowalczyk | File formats, encryption, troubleshooting, the site's engine |
What is checked before a guide is published
All of it, every time.
- Every claim about how a PDF behaves is tested against real files, using the tools on this site
- Every number - a size, a percentage, a resolution - is measured rather than estimated
- Every statement about what a tool does is checked against what the tool actually does
- Anything uncertain is stated as uncertain, in the text, not in a disclaimer at the bottom
- Nothing is published that we would not follow ourselves
How guides are kept current
Each guide shows the date it was published and the date it was last reviewed. A review means someone read it again against current behaviour, not that a script touched the file to refresh a timestamp.
Where behaviour changes - a format, a common reader, one of our own tools - the affected guides are updated and the review date moves. Where nothing has changed, the date stays where it is. An article claiming to have been updated yesterday when nothing in it changed is lying to you about something small in order to rank, and it is a reliable signal about everything else on the page.
Corrections
If something here is wrong, tell us and it will be fixed. Substantive corrections are made in the text and the review date is moved. We do not quietly edit a claim out of existence and pretend it was never made.
What we will not publish
Guides to cracking PDF passwords, removing watermarks from other people's documents, or circumventing digital rights management. Not because they would not attract traffic - they would - but because the traffic they attract is people trying to do something to a document that is not theirs.
We also will not publish a page for a tool this site does not have, a comparison written to favour a product that paid for it, or an article whose purpose is to occupy a search result rather than to answer a question.
On the use of AI
The illustrations on this site are generated. They are decorative, they are labelled as illustration in their alt text where it matters, and none of them depicts a real document, person or examination paper. The words are written by the people named above. Where a draft has been assisted, a named author has rewritten, verified and taken responsibility for every claim in it - which is the line that matters, and the one Google's scaled-content policy is actually about.
Independence
No guide on this site is sponsored, paid for or placed. There are no affiliate links. No product is recommended because of a commercial relationship, because there are no commercial relationships.
Where a guide says a tool elsewhere is better for a job than anything here, that is what it says. There are several such statements on this site, and they are there because they are true.
Questions and answers
Are the authors real people?
Yes, with stated roles and areas of responsibility. Their pages list what each one works on and what they have written.
Do you accept guest posts?
No. Everything here is written by the named team. Unsolicited guest-post offers are declined without exception.
Do you accept paid links?
No. There are no paid links, sponsored posts or affiliate arrangements anywhere on this site.
How do I report an error?
Through the contact page. Include the page and what is wrong with it, and we will check it against real files.