Editorial Policy

Everything published on the BGZaply blog is written and maintained by the BGZaply Editorial Team. This page explains the standards we hold that content to.

How guides are researched

We start from the task a reader is actually trying to complete — making a background transparent, preparing a product photo, exporting a logo — and work through that task ourselves before writing about it. Where a guide describes a file format, a colour mode or a platform requirement, we check the current official documentation for that format or platform rather than repeating what other sites say.

Requirements often differ by marketplace and by country. Where that is the case we say so and ask readers to confirm the rules that apply to them, instead of presenting one region's rules as universal.

How product instructions are checked

Steps that describe BGZaply tools are written against the live site and re-run before publishing. If a control is renamed or a limit changes, the affected guides are updated. Instructions for other software describe the current released version and note that menus move between releases.

How competitor comparisons are reviewed

Comparison articles only include facts we can verify on the provider's own site — free allowances, output resolution, pricing tiers, sign-in requirements and published privacy statements. If a detail cannot be confirmed, it is removed or phrased cautiously rather than guessed. We do not copy competitor text, invent test scores, or rank BGZaply first as a matter of course. Where we mention our own tool in a comparison, we label it as ours.

How articles are updated

Guides are revisited when a tool changes, when a platform changes its requirements or when a reader reports a problem. Substantive updates change the visible update date and the machine-readable modified date. Original publication dates are never rewritten, and a page is not re-dated for cosmetic edits.

Corrections policy

Factual errors are corrected on the page as soon as they are confirmed. If a correction changes the advice a reader would act on, we say what changed in the article rather than editing silently. Pages that are no longer accurate and cannot be fixed are rewritten, not left in place.

Reporting an error

Send the page URL and a short description of the problem through our contact page. Reports about a specific image are more useful with your browser and device details.

Separating guidance from promotion

Instructional content is kept independent of our own marketing. Where an article recommends a BGZaply tool it does so in a clearly labelled section, and the guide still explains how to complete the task with other software. We do not publish invented testimonials, customer numbers, ratings, partnership claims or accuracy statistics. Claims about speed and quality are written in language we can defend.

Our testing approach is described on the how we test page.