# Event Log Viewer (evtx, XML, CSV)

Drop an .evtx file to see time, level, event ID, provider and computer for each event. Filter by ID, level, time range or text, open the full XML of any event, and save the result as CSV or JSON. Message text cannot be rebuilt. To format ordinary XML, use XML Studio.

- URL: https://tools.itlibra.com/en/eventlog-viewer
- On-device・No upload
- Last updated: 2026-11-13

## How to use

1. 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).
2. Check the event count and the counts per event ID, provider and level. Click an ID or provider to filter by it.
3. Filter by level, event ID (several, comma-separated), provider, time range (UTC) and text, and sort by time, ID, level or record number.
4. Select a row to see the full XML of that event and a short explanation for common event IDs.
5. Save the filtered result as CSV or JSON (up to 200,000 rows). To try it, press "XML sample" or "evtx sample".

## 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

## 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.


## Supported formats

### Input

- .evtx (Windows event log)
- XML (Event Viewer "Save as XML", wevtutil qe /f:xml)
- CSV (Event Viewer "Save as CSV")

### Output

- On-screen list and detail (XML)
- CSV and JSON (the filtered result)


## 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?

Drop the .evtx onto this page. By default Windows stores logs in C:\\Windows\\System32\\winevt\\Logs. On a running PC they may not be copyable directly, so the reliable way is to make an .evtx with "Save All Events As" in Event Viewer.

### Can I open Event Viewer's "Save as XML" and CSV too?

Yes, and wevtutil qe /f:xml output as well. Event Viewer CSV only has the columns Level, Date and Time, Source, Event ID and Task Category, so there is no data column.

### Why is there no message text?

An event message is built by inserting the data into text that lives in the DLL of the program (provider) that wrote it. This tool reads only the file, so it shows the event data values instead.

### Where can I find what an event ID means?

Common IDs (14 of them) are explained when the provider matches. For others, look up the provider name plus the ID in Microsoft documentation, because providers can reuse an ID number.

### What time zone are the times in?

.evtx and XML times are UTC. CSV times are the local time Event Viewer showed, with no zone information, so they are used as written for sorting.

### It says some records could not be read

Part of the file is damaged, or the record uses something this tool does not support. The count and location are shown and the rest is listed. Please report it if it happens often with real files.
