Corrections Policy
Last updated: May 2026
This page describes how iloveimg.online handles errors in conversions and editorial content. Headline: conversion bugs and content errors are corrected when identified, with severity tiers, visible advisories where appropriate, and process review for systemic issues.
Part 1: Conversion errors
How we identify them
- Reader reports. Email info [at] iloveimg [punto] online with subject Conversion error: [format pair].
- Library updates may surface differences in conversion output.
- Periodic spot-check against ImageMagick command-line reference output.
- Browser-compatibility issues as new browser versions deploy.
Severity classification
Critical errors
Issues that materially affect users:
- Conversion produces corrupted output (file won't open in standard viewers).
- Conversion silently fails (returns input unchanged or empty file).
- Output has wrong dimensions / colour profile / encoding that breaks downstream use.
- Security vulnerability in conversion library affecting users.
Response standard: investigation within 24-48 hours; fix within 24-48 hours of confirmed error; visible advisory in corrections log.
Substantive errors
Errors that affect quality without rising to critical:
- Excessive quality loss in lossy conversions for specific input combinations.
- EXIF / colour profile handling differs from documentation.
- Edge-case input produces wrong output (e.g., very large dimensions, unusual bit-depth).
- UI displays incorrect file-size estimate.
Response standard: investigation and fix within 7 days. Note in corrections log.
Minor errors
Cosmetic / UX issues. Fixed when noticed.
Part 2: Library transitions
The conversion engine depends on third-party libraries (ImageMagick, libvips, libheif, libavif, libraw). When these update:
- Updates are reviewed before deployment, not auto-applied.
- Test conversions are run against representative format pairs before promoting an update to production.
- Where a library update changes default behaviour (e.g., ImageMagick's policy for handling specific formats), we document the change publicly.
- Where a library update breaks something for a specific format pair, we either patch the wrapper code or roll back to the previous library version.
Part 3: Editorial content corrections
Material errors
Errors that meaningfully mislead readers (misdescribing a format, claiming a library does something it doesn't, citing wrong specification version).
Response standard: correction within 7 days, visible correction note at top of page, body update.
Minor content errors
Typos, formatting, broken links. Fixed when noticed.
Part 4: Format / conversion-pair removals
A conversion pair may be removed:
- Unfixable library issues. Where the underlying library has unaddressable issues for a specific pair, the pair is retired.
- Low usage. Rarely-used pairs may be deprioritised.
- Security concern. If a format opens up attack surface (e.g., a known parser vulnerability not patched in the library), the pair is suspended until resolved.
- Legal / IP issue. Per DMCA.
Part 5: How to report
- Conversion errors: info [at] iloveimg [punto] online — Conversion error: [format pair].
- Content errors: info [at] iloveimg [punto] online — Content correction: [page slug].
- Security vulnerabilities: abuse [at] iloveimg [punto] online.
- DMCA / takedown: dmca [at] iloveimg [punto] online.
Helpful inclusions for conversion bug reports:
- Format pair (e.g., HEIC → JPEG).
- Sample input file if shareable (or a description; we don't ask you to send sensitive files).
- What output you got (file size, what tool reports it as, whether it opens).
- What you expected (output of ImageMagick command-line locally, behaviour in another converter).
- Browser / OS used.
Part 6: What we do not do
- We do not silently fix errors that affected users.
- We do not refuse to acknowledge errors out of pride.
- We do not retain conversion pairs we know to be broken.
Related pages: Format Catalog · Accuracy Disclaimer · DMCA · Contact Us · Responsible Use