How to use
Drop an .evtx, the XML or CSV from Event Viewer's "Save All Events As", or the output of wevtutil qe /f:xml, or choose it with "Choose file" (up to 200 MB).
Check the event count and the counts per event ID, provider and level. Click an ID or provider to filter by it.
Filter by level, event ID (several, comma-separated), provider, time range (UTC) and text, and sort by time, ID, level or record number.
Select a row to see the full XML of that event and a short explanation for common event IDs.
Save the filtered result as CSV or JSON (up to 200,000 rows). To try it, press "XML sample" or "evtx sample".
What it does
Reads .evtx Binary XML itself
Reads the .evtx structure (the ElfFile header and 64 KB chunks) and turns each record's Binary XML into XML, resolving template substitutions and name references. Records that cannot be read are counted with their positions and skipped.
XML and CSV on the same screen
Also reads Event Viewer's "Save as XML", wevtutil output (UTF-8 or UTF-16), and Event Viewer CSV with Japanese or English column names. CSV times have no time zone, so they are used as written.
Filters and counts
Filter by level, event ID (several), provider, time range (UTC) and text, with counts by ID, provider and level. Up to 2 million events are handled in a Worker.
Explanations for common IDs
4624, 4625, 4634, 4648, 4672, 4720, 4740, 1102, 7045, 6005, 6006, 6008, 41 and 1074 get a short explanation based on Microsoft documentation. Different providers can reuse an ID number, so it is shown only when the provider also matches.
Shows broken parts and continues
Offsets and lengths are checked before any read. Records that cannot be read are counted with their location and skipped; the rest stays usable.
Use cases
- Count failed logons (4625) in a short time and see which IP they came from
- Check whether a service was installed (7045) or the audit log was cleared (1102)
- See what was recorded around an unexpected restart (41, 6008), in time order
- Open an .evtx from another PC without needing Windows
- Filter an Event Viewer XML or CSV export and share it as a table
Supported formats
Input
Output
Capability matrix
| Feature | Support | Notes |
|---|---|---|
| Reading .evtx (Binary XML, templates) | Supported | A parser written to the format. Please report any problem found with a real file |
| Reading XML and CSV | Supported | XML in UTF-8 or UTF-16. CSV times have no time zone |
| Filtering, sorting and counts | Supported | — |
| Showing the full XML of one event | Supported | — |
| Saving as CSV or JSON | Supported | The filtered result, up to 200,000 rows |
| Explanations for common event IDs | Partial | Only 14 IDs, shown when the provider matches |
| Rebuilding the message text | Not supported | The text lives in the provider's DLL (message table), so only the event data values are shown |
| Reading the live log of a running PC | Not supported | Only files that were saved |
| Repairing an .evtx or recovering deleted records | Not supported | Unreadable records are only skipped |
| Threat detection or attack judgement | Not supported | ID explanations are plain facts, not a verdict |
| Offline use | Supported | Works without a network connection after the page has loaded once |
Limits & notes
- Files up to 200 MB. Larger files are refused before they are read.
- Up to 2 million events. Events beyond that are not read (the number read is shown).
- The Data column in the list shows the first 160 characters. The full data is in the XML detail of each event.
- Saving covers the first 200,000 rows of the filtered result.
- One event's XML can have up to 20,000 elements and depth 64, and one XML event text up to 4 MB.
Privacy & safety
The file is read only inside your browser. Nothing is sent to or stored on a server. Logs can contain user names and IP addresses, so check the saved CSV or JSON before sharing it.
FAQ
How do I open an evtx file?
Can I open Event Viewer's "Save as XML" and CSV too?
Why is there no message text?
Where can I find what an event ID means?
What time zone are the times in?
It says some records could not be read
Related tools
XML Studio — Formatter & Validator
Paste XML to format, minify or validate it. Errors show the exact line, column and cause, and whitespace that carries meaning (mixed content, xml:space) is never touched. XPath search and JSON conversion are on the same screen. Your data never leaves your device.
Universal File Inspector
Drop any file to see its real format (from the content), its structure and metadata, what to watch out for, and which tools can process it — before opening it, or before sending it to someone.
JSON Studio — Formatter & Validator
Paste JSON to format, minify or validate it instantly. Errors are shown with the exact line, column and cause, and comments or trailing commas can be auto-repaired. Your data never leaves your device.
Lockfile Diff & Dependency Tree
Compare two lockfiles to see which packages were added, removed or upgraded. You can also see why a package is installed and where several versions of one package come from. Nothing leaves your browser.
Docker Compose Studio
Convert docker run commands to compose.yaml, or compose.yaml back to docker run. A compose file is checked for syntax, the Compose Specification and common mistakes, and security points worth confirming are listed. Nothing is started or pulled, and your input never leaves your device.
Dockerfile Studio
Paste a Dockerfile to check its syntax, stages and common mistakes. Secret-looking values and points to confirm, such as curl | sh, are listed with line numbers. You can also format it or generate starter files for Node.js, Python, Go, a static site or Java. Nothing is built, and your input never leaves your device.
Last updated: