Can Logs handle a mix of formats in one paste?
Yes. Each line is detected on its own, and the format most lines use is shown as the detected format.
Messy logs in, clean logs out.
Paste log lines from any mix of sources. Logs detects each format, pulls out the timestamp, level, message, and fields, normalizes the levels, and writes it all back as JSON lines, key=value, or plain text.
Loading the toolbox.
You do not have to take our word that your data stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your data. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your data elsewhere.
2026-01-01 10:00:00 ERROR boot failed, [WARN] disk low, or INFO: ready. Timestamps in ISO 8601, with a space or a T, slash dates, bare times, and Unix epochs are recognized.level=info msg="ready" port=8080, with quoted values unescaped and plain numbers and booleans kept as numbers and booleans.Every line is detected on its own, so a paste that mixes an application log with a few syslog lines still converts cleanly. Indented lines, such as stack traces, are joined to the entry above them instead of becoming entries of their own.
Every logger spells levels its own way. Logs maps them all onto six canonical levels: trace, debug, info, warn, error, and fatal.
warning and WRN become warn.err and severe become error.critical, crit, emerg, alert, and panic become fatal.notice becomes info, and verbose becomes trace.A word only counts as a level in plain text when it is bracketed, followed by a colon, written in capitals, or comes right after a timestamp, so a message such as "error connecting to the cache" is not mistaken for a level on its own.
JSON lines puts ts, level, and msg first and keeps every other field, ready for jq, a log shipper, or a data warehouse. key=value writes logfmt, quoting any value that contains spaces, quotes, or equals signs, which is what tools such as Loki and Heroku expect. Plain writes a readable, aligned line with the level in capitals and the fields at the end.
Each format has its own copy button, and the current one can be downloaded as a file. Converting to JSON lines and back to plain text is a quick way to clean up a log before pasting it into an issue or a chat.
Tick or untick each level, including lines that have no level at all, and the output and the table update at once. The Warn and up button keeps only warn, error, and fatal, the quickest way to find what went wrong in a long log. The stats bar shows how many lines came in, how many entries they became, and how many of each level there are, so you can spot a spike in errors at a glance.
Logs often carry user IDs, IP addresses, email addresses, and sometimes tokens that should never have been logged. Logs reads them on this page and nowhere else: nothing is uploaded, nothing is saved to storage, and everything is gone when you close the tab. You can confirm it with the Network tab steps below. Even so, redact secrets before sharing any converted output.
Elsewhere in the toolbox: UUID, .gitignore, CSP, .htaccess, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.
Yes. Each line is detected on its own, and the format most lines use is shown as the detected format.
Indented lines are joined to the entry above, so a multi-line stack trace stays with the error that caused it.
No. They are parsed in this tab, kept only in memory, and never sent or stored.
ISO 8601 with or without a T and time zone, slash dates, syslog dates, bare times, and Unix epoch seconds or milliseconds. Timestamps are kept as written, never shifted between time zones.