Editorial Standards

What we publish

PDFWhisk publishes browser-based PDF tools, supporting help pages, and practical guides for common PDF tasks. Our content falls into three categories: tool pages that explain exactly how each tool works and what it is for; task guides that walk through a specific document problem from start to finish; and reference pages covering topics such as PDF file formats, browser compatibility, and privacy considerations for document handling.

We do not publish content that is outside these areas. PDFWhisk is a focused site about practical PDF tasks, and we keep it that way intentionally. Every page should help a user accomplish something specific, or help them understand something directly relevant to using PDF tools.

How pages are written

We write for people who want to get something done. That means clear task instructions first, context and explanation second. We avoid jargon where plain language works equally well. Where technical terms are necessary — for example explaining the difference between AES-128 and AES-256 encryption, or what a linearised PDF is — we define them in the same paragraph rather than assuming background knowledge.

Content is structured around actual user questions we observe in search data. If a significant number of people are asking "how do I compress a PDF for WhatsApp", that question deserves a direct answer written specifically for that context, not a generic compression guide with a passing mention. This approach produces more useful pages and avoids padding.

Instructions are tested against the live tool flow before publication where possible. If we describe a five-step process, we check that those five steps actually produce the expected outcome in current desktop Chrome, mobile Safari, and Firefox. When browser behaviour differs, we note it.

Privacy claims

Privacy claims on PDFWhisk are technically verifiable. When we say a tool runs locally in the browser, that means no file data is transmitted to any server during the operation. You can verify this yourself using browser developer tools: open the Network tab, run a conversion, and observe that no file upload requests are made.

We limit privacy claims to workflows where we can make this guarantee. We do not make blanket statements about "complete privacy" that cover future features or edge cases we have not reviewed. Where commercial elements such as advertising or analytics are present, we describe them clearly in our privacy and cookie policies rather than minimising them.

If you find a discrepancy between a privacy claim on any page and the actual technical behaviour of the tool, please contact us at hello@pdfwhisk.com. We take these reports seriously and will correct inaccurate claims promptly.

Accuracy and updating content

PDFWhisk content is reviewed when tool behaviour changes, when browser APIs change in ways that affect our instructions, or when user feedback indicates that instructions are unclear or incorrect. Core tool pages are reviewed at least every six months. Blog posts are updated when the underlying information changes materially — for example if a new browser version handles PDF processing differently, or if file size limits on commonly used portals change.

We mark significant updates with a revised date on the page. Spelling corrections and minor copy improvements are made without updating the date. If a substantial part of the advice on a page has changed, we update the date and add a note where the change is relevant to someone who has read the page before.

Commercial independence

PDFWhisk is funded by optional Pro purchases and display advertising. Neither of these revenue sources influences the content we publish. A tool that is available on the free plan is described as free. We do not rank tools higher in navigation because they generate more revenue. We do not recommend paid features when a free workflow achieves the same outcome.

Our guides link to PDFWhisk tools because those are the tools this site is built around — not because linking to them generates revenue. When we mention alternative approaches (for example, using Preview on Mac to rotate a PDF), we mention them because they are genuinely useful to some readers, even though they do not involve PDFWhisk.

Editorial ownership and corrections

PDFWhisk content is edited by James Whitfield, a writer focused on practical browser-based productivity tools. James is responsible for the accuracy of tool descriptions, task guides, and privacy claims across the site.

For factual corrections, contact hello@pdfwhisk.com with the page URL and the specific claim you believe is inaccurate. We aim to review correction requests within five working days. If the correction is substantiated, we update the page and respond to confirm the change.

We do not accept sponsored content, paid placements, or editorial contributions from third parties. All content published on PDFWhisk is written or approved by the editorial team.

Scope of guidance

PDFWhisk guides provide practical instructions for common PDF tasks. They do not constitute legal advice. Questions about the legal validity of electronic signatures, document retention requirements, or data protection obligations should be directed to a qualified solicitor or adviser familiar with your specific situation and jurisdiction. We explain what PDF tools can do technically; we do not advise on what you are legally required or permitted to do with documents in your context.

Last reviewed: May 2026.