Log viewer

Every text log opens on its Logs tab in the log viewer: the file’s lines, in order, with the columns its format has (time, level, tag, process and thread IDs, and any fields the format adds). Only the lines on screen are loaded, so a file of millions of lines scrolls as easily as a short one.

Line numbers are the ones your editor shows, blank lines included. Times and levels are read from the common log layouts, including calendar-style stamps such as Wed May 13 22:54:19 2026 and lines that open with a date and time followed by a level word such as INFO, WARN or ERROR. A log uploaded before a layout was recognised keeps its line-number-only view until you upload it again.

Filtering

Levels: one chip per level the file uses, with its line count. The first click on a chip shows that level and above; after that each click turns a level on or off.
Tag, PID and TID: each picker lists the values with how many lines hold them.
Search: type to match the line text. Where the file supports it, the .* toggle matches a pattern instead.
Filters: the builder combines conditions on any column, including time and line ranges, and shows how many lines the draft matches before you apply it.
Click a value in a row, such as a tag, to filter to it.

Every count is taken under your other filters, so a level chip shows how many lines of that level match the tag and text you picked. Each filter step is a step in your browser history: Back undoes it. When nothing matches, the viewer names the filter that removed the most lines, so you can clear just that one.

Finding your place

The density strip above the lines shows where lines cluster over time, stacked by level, and flags spikes. Click a bar to jump there, or drag across it to narrow to that range; double-click to reset.

Jump to takes a line number, or a time such as 14:02:05 read on the file’s own day. A file whose times could not be placed on a calendar shows them as written; its strip goes by line number, and Jump takes a line number or a full date and time. The viewer says so above the lines.

A line in detail

Double-click a line, or select it and press Enter, to open it beside the list (on a phone, tap it). You get every field, the full text, any logcat.ai insight that cites the line, and ways out: the lines around it with your filters paused, and the same tag or PID.

Keys: ↑ and ↓ move, Enter opens, B bookmarks the line, and / puts the cursor in the search box.

Bookmarks and saved views

Bookmarks are yours: a bookmarked line keeps its mark under any filter, and the line’s detail lists your bookmarks so you can go back to one.

Views saves the current filter and visible columns under a name. A view is yours until you share it with your workspace; a shared view’s link opens the capture with that view applied for a teammate who can open the capture.

Citations

A citation on a dashboard finding or in a report opens the Logs tab on the cited line or range, highlighted in the middle of the screen, with your own filters paused. Restore my filters brings them back. Links saved before this viewer, including citations in older reports, still open on the same lines.

Multi-file captures

A bundle’s Logs tab has two views:

On one clock shows two of its text files side by side, with times on the capture’s shared clock, and moves the other file to the same moment when you select a line. The alignment note says what the shift rests on, and files that could not be placed keep their own times and scroll on their own.
All files is the bundle’s file tree; open any file for its own dashboard and Logs tab.

The tab opens on one clock where at least one text file could be placed on the capture’s clock, and on the file tree otherwise.

A baseband capture’s Logs tab lists its decoded records instead; see Telecom.