Scope and responsibility
OfflineConvert is maintained as an independent software project. The project is responsible for the converter code, original explanatory copy, practical guides and Lab measurements published on this domain. We do not attach invented personal credentials to content; technical authority comes from reproducible behavior, disclosed methods and corrections that remain accountable to the project.
What makes a tool page publishable
- The converter must complete a representative real-file path in a browser.
- The output is checked for format-specific evidence such as signatures, dimensions, transparency, encoding, archive integrity or font loadability.
- The page states what is preserved, what may be lost, practical safety limits and at least one case where conversion is the wrong choice.
- Explanatory text must be specific to the format or workflow. Template claims alone are not considered useful content.
- No-upload claims are checked with a network monitor during conversion and can be verified by visitors with the published Network-tab procedure.
Guides and Lab studies
Guides are written around repeatable tasks and include failure modes or a validation checklist. Lab studies state the fixture, browser or tool version, measurement date, method and limitations. Raw CSV or JSON is published when a study produces a dataset. A single-fixture result is described as a single-fixture result, not a universal benchmark.
Dates, updates and corrections
Pages show a review date, and the sitemap date advances when that page's substantive configuration or article body changes. A new deployment does not automatically make every page “new.” We update material when tool behavior, browser support, a cited measurement or a documented limit changes.
To report an error, email [email protected] with the page, the claim or failing file behavior, and evidence that can be reproduced. Factual and functional corrections are prioritized over stylistic requests.
Advertising independence
Advertising may fund maintenance, but advertisers do not select which converters are built, alter test outcomes, review editorial copy, or buy placement in comparison results. Ads are visually and technically separated from file drop zones, download controls and navigation to reduce confusion and accidental clicks. Sponsored rankings and paid recommendations are not published.
Privacy boundary
Files selected in a tool stay in the browser and are not available to the project, analytics or advertising code. Analytics is opt-in and limited to coarse tool and outcome events described in the privacy policy; file names, contents, exact sizes and raw errors are excluded.
Limits of the evidence
Automated checks cover representative fixtures and known edge cases, not every file ever produced by every application. Browser vendors can change decoders, encoders and memory behavior. When a result depends on one browser version or one sample, the page must say so. Visitors should keep original files and validate converted output before deleting a source or using it in a critical workflow.