Editorial policy and verification

Last updated: 2026-04-22

FileHint is a reference site for file extensions, MIME types, and an in-browser file identifier. Our editorial priority is: the reader should know what to do with the file within a minute. FileHint is operated by Netwiz LLC (Japanese legal name: ネットウィズ合同会社) and edited by the FileHint editorial team.

1. Fact-checking

We rely on primary sources: IANA media-type registrations, RFCs, ISO/IEC, W3C, and vendor documentation.
Secondary sources (blog posts, analysis articles) are used only to supplement primaries, never as sole evidence.
Claims we cannot verify are not published; we do not pad with "may" or "sometimes" hedges.
Security content cites NVD, JVN, or MITRE with CVE identifiers.

2. Source selection order

Standards bodies (IANA, ISO, IEC, W3C, IETF/RFC)
Implementing vendors (Apple, Microsoft, Google, Mozilla, Adobe, etc.)
Primary documents cited by Wikipedia — but never Wikipedia itself.
For historical context only, we may cite well-established technical journalism.

3. Verification process

Every article clears the following before publication:

Magic bytes: sample files are checked against the spec using the File Signature Checker.
Behaviour: behaviour claims name the specific OS (Windows 11 / macOS / iOS / Android 14) and browser (Chrome, Firefox, Safari, Edge) versions tested.
Tooling: CLI and GUI steps are reproduced in a real environment; UI strings match the current release.
References: every article lists its sources at the end with stable labels; link rot is audited periodically.

4. Dangerous files & security content

Executables, macro-bearing files, and credential-containing files default to "do not open / do not run"; any necessary guidance assumes an isolated environment.
We do not publish malware analyses, proof-of-concept exploit code, or attack recipes.
We recommend hash-first lookups on services like VirusTotal and never nudge readers to upload sensitive files.
We make it explicit that "clean" on antivirus is not the same as "safe".

5. Update policy

Pages are revised as major browsers, OSes, and specs evolve.
When a notable CVE affects an extension, we update the safety notes as quickly as possible.
The Updated: YYYY-MM-DD at the bottom of each page reflects a real edit; the sitemap <lastmod> follows it.
We do not tick the date forward when nothing substantive changed.

6. Corrections

Report errors via the contact page.
Confirmed factual errors are targeted for correction within 7 days.
Material errors get a visible correction notice at the top of the affected page for a period after the fix.

7. Use of AI-assisted writing

LLMs may assist with drafts, but every article is checked against primary sources by a human editor before publication.
Statements AI-generated without verifiable citation are not published.
Citations, commands, and code are re-verified in a real environment.

8. Advertising & independence

Revenue is Google AdSense only. We do not run affiliate content, sponsored posts, or paid vendor placements.
Recommendations and rankings are independent of advertising relationships.

9. Sister services

Netwiz LLC also operates other web services, including ImageMint(imagemint.app, a browser-side image convert / EXIF / compress toolkit). FileHint articles occasionally point to a sister service when it genuinely helps the reader finish the task. We follow these rules:

Disclosure: links to sister services are explicitly labelled "operated by Netwiz LLC (the same company behind FileHint)". They are not advertisements — they are related services.
Relevance first: a sister-service CTA appears only when the reader can actually complete the article's task there. We do not paste CTAs mechanically across pages.
Neutral framing: we do not hype sister services or disparage competitors. Alternatives — built-in OS tools, well-known open source — are still mentioned where relevant.
Not affiliate: sister-service links carry no referral tags or tracking parameters. There is no revenue share or per-click payout.