.WER

WER File

Windows Error Report
Ask a question
QUICK ANSWER

A WER file is a plain-text Windows Error Report created automatically when an application or the system crashes. Open it with Notepad or Notepad++ to read which program failed and why. The file is safe to delete - Windows recreates reports as new crashes occur.

Developer: Microsoft Category: System Files MIME: text/plain
OPENS ON Windows
Related: .NOMEDIA · .DLL · .TMP · .LNK

On this page

19k+ extensions indexed
Last reviewed Aug 13, 2026

Not sure what your file is?

Drop any file into our identifier - we read just the first bytes to name the format.

Identify a file

What is the WER file format?

A .wer file is a Windows Error Report generated by the Windows Error Reporting (WER) service, a component built into Windows Vista and all later releases by Microsoft. The .wer file is a plain-text file that captures error information for both application crashes and operating-system faults that have occurred on the machine.

The file uses an INI-like structure - [WER...] section headers followed by Key=Value lines - and is typically encoded in UTF-16 LE (little-endian), beginning with the byte-order mark FF FE. It records fields such as the faulting application name and version, the module that triggered the fault, the OS build number, the exception code, and bucket parameters used by Microsoft's crash-analysis back end.

Importantly, the .wer file is the human-readable metadata for a crash, not the crash data itself. The actual memory snapshot lives in companion .mdmp and .hdmp files stored in the same report folder. When used in combination, the .wer metadata and the minidump files together provide the information needed to diagnose the cause of the crash.

The .wer file is generally stored at the following locations on Windows:

  • C:\Users\<USER>\AppData\Local\Microsoft\Windows\WER\ReportQueue
  • C:\Users\<USER>\AppData\Local\Microsoft\Windows\WER\ReportArchive
  • C:\ProgramData\Microsoft\Windows\WER\ReportQueue
  • C:\ProgramData\Microsoft\Windows\WER\ReportArchive

The files can be opened with any text editor such as Notepad, or reviewed via Windows Event Viewer.

Security & safety

RISK: LOW

WER files are harmless plain-text logs - they cannot execute and contain no document content. They are safe to delete (Windows recreates them as needed); Disk Cleanup and Storage Sense remove them under "Windows Error Reporting Files". One minor privacy note: a report can include the full path of the crashed program and, for some events, snippets of in-memory strings, so avoid posting raw WER/dump files publicly. The only real-world "risk" is being tricked by fake "error report" pop-ups or scam tools promising to "fix .wer errors" - the file is a symptom report, not something that needs repairing.

Format details

in a nutshell
FULL NAMEWindows Error Reportaka WER file, Windows Error Reporting report
DEVELOPERMicrosoftsince 2006 (Windows Error Reporting redesigned in Windows Vista)
CATEGORYSystem Files
MIME TYPEtext/plain
TYPEPlain-text key/value report (UTF-16 LE)
This extension is also used by…
  • WERCONFIG / WER internal metadata - Some WER folders contain Report.wer alongside WERInternalMetadata.xml and triage .txt files for the same crash event.
MAGIC BYTES · FILE SIGNATURE
OFFSET
0001
HEX
FFFE
ASCII
··
No fixed format signature. WER files are plain text, almost always UTF-16 little-endian beginning with the BOM FF FE; the first readable text is typically "Version=1" or a "[" section header. Some WER reports are ASCII/UTF-8 without a BOM.

Programs that open WER files

Windows2 apps
Notepad Open-source Open the file; it auto-detects UTF-16 encoding and shows the sections clearly. Better for long reports than Notepad.
Event Viewer Built-in Not for the .wer file itself: open eventvwr.msc > Windows Logs > Application to see the same crash events with context. Reliability Monitor (perfmon /rel) shows a friendly timeline.

Technical details

deep spec
EncodingUTF-16 LE (little-endian) with BOM FF FE; occasionally ASCII or UTF-8 without BOM
Magic bytesFF FE at offset 0 (UTF-16 LE BOM); no fixed binary signature - first readable text is typically "Version=1" or a "[" section header
File structureINI-like plain text: [WER...] section headers followed by Key=Value lines
Internal version field"Version=1" present at the top of the report body
MIME typetext/plain
Typical file size1 KB - 30 KB
DeveloperMicrosoft
Associated OSWindows Vista, 7, 8, 10, 11 and Windows Server editions
Default storage paths%LOCALAPPDATA%\Microsoft\Windows\WER and %ProgramData%\Microsoft\Windows\WER (ReportQueue and ReportArchive subfolders)
Companion file types.mdmp and .hdmp minidump files co-located in the same report folder; may also include .etl event trace logs
Generation processCreated automatically by WerFault.exe or WerFaultSecure.exe when an application or system fault is detected
Key recorded fieldsFaulting application name, version, module path, OS build, exception code, and bucket ID for Microsoft crash analysis
CompressionNone - stored as uncompressed plain text
Report lifecycleReports land first in ReportQueue (pending upload); moved to ReportArchive after submission or local retention
Released2006 (Windows Error Reporting redesigned in Windows Vista)
Latest versionWindows Error Reporting (current in Windows 11; format unchanged since Vista)
Specificationlearn.microsoft.com

WER conversions

Community Q&A

asked by users
Ask a quick question
Get help from people who work with WER files. Be specific - include your system and software version.
No account needed · answers usually within a day

No questions yet - be the first to ask about WER files.

Frequently asked questions

What is a WER file and can I delete it?
It is a Windows Error Report - a small text log describing an app or system crash. Yes, it is safe to delete; Windows recreates reports as crashes happen. Disk Cleanup removes them under 'Windows Error Reporting Files'.
How do I open a WER file?
Open it with any text editor - Notepad or Notepad++. The contents are readable Key=Value lines naming the faulting program, module and error codes.
Where are WER files stored in Windows?
Under %LOCALAPPDATA%\Microsoft\Windows\WER (per user) and %ProgramData%\Microsoft\Windows\WER (all users), each with ReportQueue and ReportArchive subfolders.
Does the WER file contain the actual crash dump?
No. The .wer file is only the metadata. The real crash data is in companion .mdmp (minidump) or .hdmp (heap dump) files in the same report folder.
Will deleting WER files fix the crashes?
No. The report only describes the crash; deleting it removes the log, not the cause. Use the information inside (faulting module, app version) to update the driver or app responsible.
Why are there so many WER files taking up space?
Windows keeps a report for each crash/hang in the ReportArchive folder. Frequent crashes pile up. Clear them with Disk Cleanup or Storage Sense; they are safe to remove.

References

1Microsoft Learn - Windows Error Reporting (WER)learn.microsoft.com
2Microsoft Learn - WER Settings and report storagelearn.microsoft.com

Keep exploring

across the database

Top extensions this week

1.AQQAQQ Instant Messenger File
2.CRDOWNLOADChrome Partial Download File
3.MDMarkdown Document
4.BINCD/DVD Disc Image (BIN/CUE)
5.NOMEDIAAndroid No-Media Marker File
6.PARTPartial Download File
7.RPMSGRestricted Permission Message
8.EXEWindows Executable (Portable Executable)
9.AVIFAV1 Image File Format (AVIF)
10.DBSQLite Database File

Related extensions

.NOMEDIAAndroid No-Media Marker File
.DLLDynamic Link Library
.TMPTemporary File
.LNKWindows Shell Link (Shortcut)
.PKGmacOS Installer Package
.ETLEvent Trace Log

Free file tools

An in-browser file identifier and image converter - everything runs on your device.

Open the toolbox

Browse file extensions A-Z