Skip to content
| Marketplace
Sign in
Visual Studio Code>Data Science>BigLogViewNew to Visual Studio Code? Get it now.
BigLogView

BigLogView

wasdzy

|
1 install
| (0) | Free
View, search, filter and tail huge log, JSON Lines, CSV and plain text files (gigabytes) without loading them into memory.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

BigLogView

Huge file viewer for VS Code — open, search, filter and tail multi-gigabyte logs, JSON Lines, CSV and plain-text files without loading them into memory.

Install it from the VS Code Marketplace, or from the packaged biglogview-*.vsix. It is a fork of BigView — see Fork and licence at the end.

中文说明:README.zh-CN.md


Screenshots

A log file with a keyword query (error|timeout): every keyword is painted in its own color, worker-7 carries a colored mark, and the matching lines are listed below.

BigLogView showing a log file, keyword colors, a color mark and the results panel

JSON Lines with syntax colors taken from the editor theme, and the same keyword rules:

BigLogView showing a JSON Lines file with syntax highlighting

CSV with a detected delimiter, a header row and a table view:

BigLogView showing a CSV file as a table

All three are screenshots of BigLogView itself, taken with demo data. They also travel inside the VSIX, so a packaged install shows them without a network.

Features

  • Any file size — opens multi-gigabyte files right away; the first page appears in tens of milliseconds while the file is indexed in the background
  • Low memory — keeps a compact line index, never the file itself; only the lines on screen are read
  • Instant reopen — the index is cached on disk and reused until the file changes
  • Whole-file search — literal keywords with | (any), & (all) and > (in order) rules, case-insensitive by default, with streaming results, progress and a results panel
  • No regex syntax — you type words, not patterns: error|fail finds either word, ANR&timeout needs both, start>init>ready needs them in that order
  • Keyword rules everywhere — the same expression syntax works on logs, JSON Lines, CSV and plain text, and feeds the filter, export, results list and F3 navigation
  • Filter — show only the matching lines; switching is instant. The search bar button reads Only matches, and All lines once the filter is on
  • Color marks — select text, right-click and paint every occurrence of it in one of six colors (red, green, blue, orange, purple, yellow), like the earlier personal log viewer; right-click → Clear Marks removes them, and marks belong to the file so they survive a reload (turn that off with biglogview.marks.persist); marks show up in the results list too, so the excerpts read like the file
  • Copy All Filtered Lines — right-click → Copy All Filtered Lines copies every line the filter kept, in file order; it stops at 8 MB and the status bar says how many were copied, with Export Filtered Lines for the rest
  • Copy Line — right-click any row → Copy Line puts that line on the clipboard whole, even when the view cut a very long line short; the results list has the same entry and copies the file line behind the excerpt
  • Keyword colors — a multi-keyword query gives every keyword its own highlight color (red, green, blue, orange, purple, yellow, in order of appearance) in both the file view and the results list, with a legend above the results naming each keyword; a single keyword keeps the theme's match highlight
  • Export — write the filtered lines to a new file
  • Log files — lines colored by level, timestamps recognized, and a time-window box of its own on the far right of the search bar that narrows any query to a time span; the box turns red on an unusable bound before the search runs, and the header names the window in force
  • JSON Lines — syntax highlighting in the colors your theme uses for JSON, a details panel with fields and pretty-printed JSON, field filters like level=error
  • CSV / TSV — delimiter detection, header row, table view with resizable columns
  • Plain text — .txt and other text files opened with BigLogView get whole-file search, filter, export and tail; they stay with the regular editor by default, and BigLogView is listed in Reopen Editor With… for them
  • Tail — new lines appear as the file grows; the view follows them when scrolled to the end, and an active search or filter keeps up
  • Log rotation — renamed, truncated, deleted or recreated files are detected and indexed again
  • Theme-aware — adapts to any VS Code color theme
  • Read-only and offline — never changes your file and sends nothing anywhere

Performance

Measured with npm run bench -- --size 200m on a Windows 11 desktop with an SSD, on a 200 MB log of 1,030,983 lines:

Measured Budget
First page (before indexing finishes) 216 ms < 300 ms
Full index 350 ms < 12 s
Reopen (index cached on disk) 37 ms instant
Literal search, whole file 436 ms < 6 s
Peak memory (RSS) 124 MB < 250 MB
Go to line (p99) 1.0 ms < 50 ms
Export 97,120 lines 1.3 s info

Costs grow roughly linearly with file size; the 1 GB and 5 GB cases are not measured on this machine, so they are not claimed here. Your disk and CPU decide the rest.

Getting Started

  1. Install it — search for BigLogView in the Extensions view (or ext install wasdzy.biglogview), or install the packaged VSIX with code --install-extension biglogview-0.4.1.vsix / Extensions → … → Install from VSIX…
  2. Open a .log, .jsonl, .ndjson, .csv or .tsv file — BigLogView is the default editor for them
  3. Or right-click any file in the Explorer → Open File in BigLogView

To open one of these files in the regular text editor, use Reopen Editor With… → Text Editor.

.txt files keep the regular text editor by default. When one is too big to edit, right-click it in the Explorer → Open File in BigLogView (the first item in the context menu), or use the editor title's Reopen Editor With… → BigLogView, Open With… → BigLogView, or the command BigLogView: Open File in BigLogView. Inside BigLogView the file is read-only.

Supported Formats

Format Detected by Features
Log .log, content Level colors, timestamps, time range filter
JSON Lines .jsonl, .ndjson, content Syntax highlighting, details panel, field filters
CSV / TSV .csv, .tsv, content (, tab ; \|) Table view, header row, resizable columns
Plain text .txt, .text, anything else Search, filter, export, tail

.txt is plain text by definition: its lines are never shown as a table or colored as a log, unless the content is overwhelmingly JSON Lines. Files with an unknown extension are sniffed (JSON Lines, log, DSV, text). .txt files keep the regular text editor by default — open them in BigLogView when they are too big, with Reopen Editor With… → BigLogView or right-click → Open File in BigLogView.

The format is detected from the extension and the first lines of the file. Change it with BigLogView: Change Format… or by clicking the format in the status bar; the choice is remembered per file.

Field filters (JSON Lines)

Filter Matches
level=error Field equals the value
user.id=42 Nested field
msg~timeout\|refused Field matches a regular expression

Click a field in the details panel to filter by its value.

Keyword rules (any format, the only search syntax)

The search box takes a keyword expression — there is no regular-expression mode and case is ignored unless you turn on Aa (Alt+C):

Syntax Rule Example
a\|b\|c Any of them (OR) error\|fail\|crash
a&b All of them, any order (AND) ANR&timeout
a>b>c In this order on the line (ORDERED) start>init>ready

Groups combine as ORs: Error|Fatal&Watchdog matches a line with Error, or a line with both Fatal and Watchdog. Within a group & is applied before >, and keywords may not overlap in an ORDERED rule (a>a needs two separate as). A single word is a plain substring search, so typing timeout just finds every line containing timeout — case-insensitively by default. Several keywords are painted in different colors, so Error|Fatal&Watchdog makes it obvious which word matched where. Typing ( or [ is safe: those characters are matched literally, never as a pattern. Filtering, export, the results list and F3 navigation all work on the matches.

Commands

Command Description
BigLogView: Open File in BigLogView Open any file in BigLogView
BigLogView: Go to Line... Jump to a line number
BigLogView: Find in File Focus the search bar
(search bar Search button) Same as Enter: run a changed query or jump to the next hit
BigLogView: Find Next / Find Previous Jump between matches
BigLogView: Toggle Filter (Show Only Matching Lines) Show only the matching lines
BigLogView: Export Filtered Lines Save the filtered lines to a new file
BigLogView: Change Format... Choose Log, JSON Lines, CSV, TSV or plain text
(Open With / Reopen Editor With) .txt, .text, .log, .jsonl, .ndjson, .csv, .tsv are offered there; only the formatted ones open in BigLogView by default

Settings

Setting Default Description
biglogview.marks.persist true Keep right-click color marks after the file is closed and reopened. Off: marks last only while the editor is open

Keyboard Shortcuts

Action Windows / Linux macOS
Find Ctrl+F Cmd+F
Next / previous match F3 / Shift+F3 Cmd+G / Shift+Cmd+G
Go to Line Ctrl+G Ctrl+G
Match case Alt+C Alt+C
Close search Escape Escape

Limitations

BigLogView is built for reading and searching. It does not do the following:

  • No sorting of lines or CSV columns — sorting a multi-gigabyte file needs a copy of it
  • No editing — the file is read-only
  • Local files only — no remote, SSH or virtual file systems yet
  • UTF-8 and UTF-16 — a UTF-16 file with a byte-order mark (LE or BE) is decoded into a UTF-8 copy under the extension storage and read through it, so tails keep working; other encodings (UTF-32, legacy code pages) are not decoded, and files with NUL bytes but no UTF-16 mark are still treated as binary
  • Timestamps without a time zone are taken as UTC — unusual timestamp layouts may not be recognized by the time range filter
  • CSV fields containing line breaks are shown as separate lines — BigLogView's unit is a line
  • Search works line by line — a pattern cannot match across a line break
  • Very long lines are cut at 16 KB in the view (search and export still see the whole line); the JSON details panel reads up to 1 MB of a line
  • Legacy .tmTheme color themes — JSON Lines highlighting falls back to default colors
  • Index cache lives in VS Code's extension storage — at most 500 MB in total, entries unused for 30 days are removed

Build

npm install
npm run build              # extension, workers and webview bundles
npm run watch              # dev mode with auto-rebuild
npm test                   # unit tests
npm run test:integration   # VS Code integration tests (BIGLOGVIEW_LARGE=1 / BIGLOGVIEW_HUGE=1 add 1 GB / 5 GB files)
npm run bench              # memory and speed per phase

Press F5 in VS Code to launch the Extension Development Host.

Fork and licence

BigLogView is a fork of BigView by fogio, released under the MIT licence. Modifications in this fork: .txt / .text support (search, filter, export, tail, and an entry in Reopen Editor With…), the keyword-rule search syntax ported from the author's own earlier personal log viewer replacing the regular-expression UI, case-insensitive search by default, UTF-16 sources read through a decoded copy, colored text marks, per-keyword highlight colors with a legend, the time-window box, the Search button and the "Only matches / All lines" toggle, the biglogview.marks.persist setting, and the rebrand to BigLogView.

That earlier personal viewer is the author's own tool, so the syntax and the mark behaviour reused from it carry no third-party attribution.

The original MIT notice is kept verbatim in LICENSE; the fork, its origin and its changes are described in NOTICE. MIT permits renaming, modification, commercial use and redistribution as long as the original copyright notice and permission text travel with the code — they do.

License

MIT — see LICENSE.

© 2026 wasdzy (BigLogView: this fork, its changes and its icon). Based on BigView, © 2026 fogio, used under the MIT licence; the upstream notice travels unchanged in LICENSE and the changes are listed in NOTICE.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft