All Tools View Categories About Contact Privacy

Log to Excel (XLSX) Converter

Turn log lines into a real .xls spreadsheet — columns from key=value fields, numbers stay numbers, preview live.

Runs entirely in your browser — logs never leave this page.

About Log to Excel (XLSX) Converter

Spreadsheets are where logs get analyzed — filtered, pivoted, charted and shared with people who will never open a terminal. But log files are text, and copying raw text into Excel is a mess of misaligned columns, numbers stuck as strings and a single "everything" column nobody can filter. Log to Excel Converter turns a batch of log lines into a real, openable spreadsheet in one paste, entirely in your browser, then hands you a .xls file to download.

The parser recognizes the common log dialects — bracket timestamps like [2026-08-15 09:12:33] [ERROR] [api], plain timestamp LEVEL category lines, key=value trails, embedded JSON payloads, JSONL and syslog headers — and maps each line to its own spreadsheet row. Timestamp, level, category and message become fixed leading columns, and every key=value pair found in a line becomes its own dynamically-added column, so fields like user_id, ip, status or duration land in the header automatically rather than staying buried inside a message string. Nested JSON payloads such as payload={"region":"eu","tier":3} are flattened into dotted columns like region and tier so even structured sub-objects become filterable cells instead of opaque text.

Enable number typing and values that are purely numeric — or numeric with a trailing unit, like attempts=3 or duration=24ms — are typed as real Excel numbers instead of text, so SUM, AVERAGE and numeric sort work immediately without a manual "convert to number" pass in Excel first. Values that only look numeric in part, such as an IP address or a version string, are correctly left as text. Toggle timestamp normalization to write every ts column as UTC ISO 8601, or leave it off to get a plain, spreadsheet-friendly date-time string instead.

Before you download anything, a live preview table shows exactly what the spreadsheet will contain — the same columns, the same rows, numeric cells right-aligned — so you can catch a misdetected format or a missing column before it reaches a colleague. The download uses the Excel 2003 XML (SpreadsheetML) format: a single self-contained XML file that Excel, LibreOffice Calc and Google Sheets (via File > Import) all open without plugins. Everything — parsing, typing, flattening and XML generation — happens locally; your log data is never sent anywhere.

Features

  • Real spreadsheet output: a .xls file in Excel-compatible SpreadsheetML XML format, ready to open.
  • Auto-detect parsing: bracket, plain, key=value, JSONL and syslog styles recognized per line.
  • Fixed columns: timestamp, level, category and message columns from every line.
  • Dynamic field columns: key=value pairs and flattened JSON payloads become their own spreadsheet columns.
  • Number typing: purely numeric values, and numeric values with a trailing unit like 24ms, become real Excel numbers for SUM and sorting.
  • Live preview: see the exact table before downloading.
  • Configurable sheet name: rename the worksheet to suit your project.
  • Header toggle: include the header row or export data only.
  • Timestamp options: UTC ISO 8601, or a plain spreadsheet-friendly date-time string.
  • Skipped-line reporting: lines that fail to parse are listed, not silently dropped.
  • Local processing: everything runs in your browser, nothing uploaded.

How to Use

  1. Paste your logs. Drop any number of log lines into the input box, or click Load sample to try a realistic multi-format feed.
  2. Choose the parser. Auto-detect handles most feeds; pin a format when a feed is unusual.
  3. Set spreadsheet options. Name the sheet, choose number typing and key=value field extraction, decide on the header row, and pick timestamp handling.
  4. Review the preview. The live table shows the exact columns, rows and numeric formatting your file will contain, plus any lines that could not be parsed.
  5. Download. Save the .xls file and open it in Excel, LibreOffice or Google Sheets.

Examples

Example 1 — Weekly error triage. Export a week of application logs to a spreadsheet, sort by level and date, and pivot error counts by category to find the service with the most failures.

Example 2 — Response time analysis. Access logs carry duration=24ms. With number typing enabled, the numeric part becomes a real number — chart the average and p95 response time straight from Excel without a find-and-replace pass first.

Example 3 — Sharing with non-technical teams. Give support a filterable Excel file of user events with clean columns (ts, level, user_id, action) instead of a wall of raw text they would have to read line by line.

Example 4 — Auditing. Convert a compliance export to a spreadsheet, add your own reviewer columns, and format the audit trail for review by non-engineers who need Excel, not a log viewer.

Example 5 — Security reporting. Aggregate login failures by IP with number typing on the attempt counts, then use Excel pivots on the converted columns to build a weekly security report in minutes.

Benefits

  • Analyze in Excel: logs become a filterable, sortable, pivotable spreadsheet.
  • No uploads: the .xls file is generated entirely in your browser.
  • Columns that make sense: fields and flattened payloads become named columns automatically.
  • Numbers stay numbers: SUM and AVERAGE work on real numeric cells, even values like 24ms.
  • Preview before you download: verify the table instantly.
  • Nothing silently dropped: unparsable lines are reported, not discarded.
  • Openable everywhere: Excel, LibreOffice and Google Sheets support the format.

Frequently Asked Questions

How does this create an Excel file without any upload?
The converter builds a SpreadsheetML (Excel XML) document in your browser with one column per field and one row per log line. You download it as a .xls file that Excel, LibreOffice and Google Sheets open natively — nothing is sent to a server.
Which log formats are supported?
Bracket formats like [2026-08-15 09:12:33] [ERROR] [api] message, plain timestamp LEVEL category lines, key=value lines, JSONL lines and syslog-style lines. Auto-detect picks the right parser per line, or you can pin one format manually.
What columns does the spreadsheet have?
A timestamp, level, category and message column, plus one column for every key=value field found in the logs, such as user_id, ip, status or duration. Columns are created automatically from the data.
Can I control how values are typed?
Yes. Enable number typing and numeric values (attempts=3, duration=24ms parses the 24) become real numbers in Excel so SUM, AVERAGE and sorting work. Disable it and everything stays text.
How do I open the downloaded file?
The file downloads with an .xls extension in Excel 2003 XML format. Double-click to open in Excel or LibreOffice, or import it into Google Sheets via File > Import. Some browsers may warn because the file is XML-based — choose Open anyway.
Is my log data uploaded?
No. All parsing and spreadsheet generation happens locally in your browser; nothing is sent to a server, stored or logged.