Editorial policy
Last updated: 2026-11-10
This policy describes how content on Image2Base64 is written, verified, updated, and corrected.
What these pages are for
The site publishes three kinds of pages. Converter pages host a working tool and explain exactly what that tool does to a given format — what survives a JPEG re-encode, what happens to transparency, what a HEIC file turns into. Guide pages cover the tasks around the tools: converting, resizing, embedding images in HTML or Markdown, and getting Base64 images to render inside email clients and third-party APIs. Photo privacy pages show people what their pictures carry — camera details, timestamps, location tags — and help them remove it, EXIF and GPS included. Every page falls into one of these groups, and none of the content is syndicated or purchased.
Accuracy
- All tools execute inside your browser via the FileReader and canvas APIs. Pages never imply server upload or cloud processing, and readers can verify that themselves in the Network tab.
- Format notes (transparency, animation, MIME prefixes) must match real browser behavior. Before an instruction is published, it is run in current versions of Chrome, Safari, and Firefox, and the page describes what those tests showed. Where the browsers differ, the page says so rather than averaging the differences into a wrong middle ground.
- .jpg and .jpeg are the same image format; the site keeps one encode URL (/jpg-to-base64) and redirects the alias instead of maintaining duplicate pages.
Sourcing
Claims come from two places: browser documentation published by the engine vendors, and first-hand testing on the machine the site is written on. Numbers are never invented — the size inflation from Base64 encoding, for example, follows from the encoding arithmetic itself (4 characters for every 3 bytes), not from a survey. A claim that cannot be checked by test or documentation does not go in, and pages are written from that evidence rather than paraphrased from other converter articles.
Update policy
Browsers change, so pages are re-checked when they do: new canvas behavior, changed defaults, or a shift in how an email client treats data URIs each trigger a review of the affected pages. Every page carries a last-updated line under the heading, and that line moves only for substantive edits — rewritten guidance, changed behavior notes, new tests. Typo fixes and broken-link repairs do not move the date, because the date is a freshness signal and keeping it honest matters more than making a page look new. Questions that keep arriving by email end up answered on the FAQ instead of staying scattered in replies.
Corrections
Corrections go to jeromell@be-winner.com. Include the page URL and the suggested fix; a report with both can usually be verified and applied in one pass. Verified errors are fixed on the page itself, and if the fix is substantive, the last-updated line changes with it. Reader corrections are handled the same way as errors found in-house: the page gets fixed, not defended. Questions about how the site is run can go to the same address or through the contact page.
Advertising
The site is funded by Google AdSense, and that money is kept visibly separate from the content. Ads never appear inside converter controls or between a tool's input and its output, and guides contain no paid placements or sponsored recommendations. Ad cookies and vendor details live on the privacy policy; authorized sellers are listed in ads.txt. What a page says about a format is decided by testing, not by any advertising relationship.