About FileTypeError.com

What this site is

FileTypeError.com is a free reference for people trying to fix a specific problem with a specific kind of file. That covers the "file type not supported" message that appears when an app refuses to open something, a document that opens but looks corrupted, an archive that won't extract, a video that plays sound but no picture, a RAW photo a Windows PC won't preview, and the many other ways files manage to break in everyday use.

Each guide is written around one concrete problem and follows the same structure: what the error usually means, the safest fix to try first, the more involved approaches when the first one doesn't work, and a short note on how to prevent the same issue in future. The goal is for a reader to land on a page, understand what's happening, and either fix the file or know it's beyond rescue — without having to read a wall of text first.

Who it's written for

The audience is broad on purpose, because file errors don't care who you are. The guides assume only that a reader can install software, navigate their operating system, and copy files between folders. Where a step needs deeper technical context — for example checksums, codecs, container formats, or character encodings — that context is explained inline rather than assumed.

In practice, the people who land here are a mix of:

• Everyday users who've been sent a file they can't open
• Office workers dealing with a document that suddenly refuses to load
• Photographers and editors handling RAW, PSD, and project files across machines
• Students working across mixed software environments
• IT staff and support engineers looking for a clear page to send to a user

What we cover

Coverage is organised by the kind of file involved, because that's how readers usually arrive — knowing the file extension and the symptom, but not the underlying cause. The main sections are:

• Document errors — PDF, DOCX, XLSX, RTF, ODT, EPUB, CAD, CSV, TXT, LaTeX and more
• Image errors — JPG, PNG, HEIC, WebP, TIFF, BMP, RAW (CR2, DNG), SVG, PSD, GIF, vector and 3D formats
• Audio & video — MP3, FLAC, WAV, AAC, MP4, MOV, MKV, AVI, WebM, OGG, codecs and project files
• Archives — ZIP, RAR, 7z, TAR.GZ, BZ2, XZ, CAB, ISO, DMG and legacy formats
• Mobile devices — iOS, Android, file transfer, sync and storage
• Programming files — JSON, XML, YAML, CSS, JS, TS, Python, Rust, Swift, Java, C++, Docker, Kubernetes and database formats
• Common problems — corruption, recovery, conversion, cross-platform issues and the underlying concepts

Topics outside this scope — for example reviews of unrelated software, opinion pieces, or news roundups — are deliberately not part of the site.

How the content is produced

The guides are written using general, well-established knowledge about each file format and the software ecosystems around it. Steps reference functionality built into widely available tools rather than obscure or short-lived software, so a guide stays useful even as specific versions move on.

When a guide mentions a third-party tool, the goal is to describe what the tool does and when it's appropriate, not to push readers towards any particular product. Free options are preferred where they work; paid options are mentioned where they genuinely add something that free tools can't do.

Pages are reviewed periodically and updated when the underlying advice changes — for example, when an operating system adds native support for a format that previously required a third-party tool, or when a long-standing compatibility issue is resolved upstream. Where a page has been reviewed, a "Last reviewed" date is shown near the top.

What this site is not

FileTypeError.com is an editorial reference site, not a data recovery service. We don't take files from readers, run scans, or perform repairs on anyone's behalf. For genuinely irreplaceable data that doesn't respond to the consumer-level methods described in the guides, a professional data recovery service is the right next step.

The site also isn't a substitute for the documentation of the specific software a reader uses. Guides explain the general approach and the reasoning behind it; the exact menu names and shortcuts in any given application can shift between versions, and the application's own help should always take precedence over a third-party write-up when something doesn't match.

Editorial principles

• Safety first. Recovery steps are ordered from least to most invasive, so a reader doesn't make a recoverable problem worse.
• Try the boring fix first. A guide that recommends specialist software before suggesting a re-download or a software update is wasting the reader's time.
• Explain why. Knowing why an error happens makes the fix easier to apply and helps prevent the same problem recurring.
• No fake urgency. Files are usually less damaged than the error message implies, and panic leads to bad decisions.
• Honest about limits. Where recovery is unlikely, the guide says so rather than implying that one more tool might work.

Get in touch

For corrections, content suggestions, or any other question, please use the contact page — there's one email address that handles everything.