Microsoft 365, AD and Windows · #38

Online Windows Event XML Viewer

Turns event XML from Event Viewer or PowerShell into a readable table and CSV.

  • Data is processed in your browser and not sent to a server
  • Export: CSV

Tool

.xml, up to 20 MB. The file does not leave your browser.

A single or several under .

What does this tool do?

The XML on an event's 'Details' tab in Event Viewer names the EventData fields, but comparing several events is hard. The tool puts one or many events into a table, sorts them by UTC time and shows EventData as Name=Value pairs in one column.

How to use it

  1. In Event Viewer use 'Save Selected Events › XML', or wrap the output of Get-WinEvent -FilterHashtable @{LogName='Security';Id=4740} -MaxEvents 50 | % { $_.ToXml() } in <Events>.
  2. Select the file or paste the XML and press Calculate.

Fields

XML file
.xml, up to 20 MB. The file does not leave your browser.
or XML text
A single or several under .

Worked example

InputValue
or XML text
<Events>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}"/><EventID>4624</EventID><Level>0</Level><TimeCreated SystemTime="2026-11-16T07:41:03.1234567Z"/><EventRecordID>884211</EventRecordID><Computer>DC01.contoso.local</Computer></System><EventData><Data Name="TargetUserName">ayilmaz</Data><Data Name="TargetDomainName">CONTOSO</Data><Data Name="LogonType">3</Data><Data Name="IpAddress">10.20.0.57</Data></EventData></Event>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Security-Auditing"/><EventID>4740</EventID><Level>0</Level><TimeCreated SystemTime="2026-11-16T07:45:10.0000000Z"/><EventRecordID>884300</EventRecordID><Computer>DC01.contoso.local</Computer></System><EventData><Data Name="TargetUserName">akaya</Data><Data Name="TargetDomainName">PC-0043</Data></EventData></Event>
</Events>

Expected result: 2 events: 07:41:03Z 4624 (ayilmaz, LogonType 3, 10.20.0.57) and 07:45:10Z 4740 (account akaya locked out from PC-0043).

In event 4740 the TargetDomainName field shows the client computer that caused the lockout. Check whether akaya has a session or mapped drive with an old password on PC-0043.

Method and assumptions

The XML is read with a safe parser (DOCTYPE/ENTITY rejected). For each Event: Provider/@Name, EventID, Level, TimeCreated/@SystemTime, Computer and EventRecordID from System; Data elements from EventData (or UserData).

SystemTime is UTC; the table is sorted by time. Level: 1 critical, 2 error, 3 warning, 4 information, 5 verbose; security audit events usually have 0.

Using the result and troubleshooting

To build a timeline from a series of events, take the CSV into the Security Incident Timeline Builder.

Limits and common mistakes

  • Binary EVTX files are not read; export to XML first.
  • Event messages (RenderingInfo) are not shown as localized text; only raw fields.
  • At most 5,000 events.

Frequently asked questions

Can I open an EVTX file directly?

No. EVTX is binary; open it in Event Viewer and save as XML, or use wevtutil qe file.evtx /lf /f:xml.

Related tools and service

Related service: SIEM Deployment and Security Logs

Systems online tools · See all online tools