Editorial policy

Image guidance should make a decision clearer, not multiply pages.

PixelProof is independently maintained around practical image workflows. This policy explains how the site separates reviewed guidance from a tool interface, keeps claims bounded, and removes pages that do not add a distinct answer.

01 · Review method

Start with a real decision

A guide is retained only when it helps someone choose a format, dimensions, crop treatment, safe area, or document workflow. A keyword variation by itself is not a reason to publish another page.

02 · Review method

Scope each claim to its evidence

Requirements that come from a platform, public authority, or technical standard are linked to the relevant primary source where possible. The source supports only the claim beside it; it is not treated as a blanket endorsement of the whole page.

03 · Review method

Test the product-specific part

Workflow notes identify what was checked in PixelProof itself: crop versus pad behavior, local browser processing, output choices, and the final manual destination check. A product test does not replace the destination's own current rules.

04 · Review method

Show review dates and limitations

Reviewed guides display their review date and, when a source is used, the source date. When a rule may vary by country, account, device, or publishing surface, the page states that the destination is the final check.

Content lifecycle

Keeping the public library useful means consolidating as well as adding.

Corrections and disclosures

See an outdated requirement or a misleading workflow note?

Send the page URL, destination, and the correction or expected result. The site currently does not load advertising code; the privacy policy is the source of truth if that operating model changes.