Log viewer for Chrome: open, search, filter, and tail .log files locally with regex, level colors, and no uploads.
Users
81
+20 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#91K
#76K among extensions
Version
1.0.2
updated 16 Sep 2026
Users
monthly, 4 months
Latest, 19 Oct 2026:81 usersMove the mouse over the chart for any month
Ratings count
monthly, 4 months
Latest, 19 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Log Viewer & Search
Log Viewer & Search is a log viewer chrome extension for developers, DevOps teams, QA engineers, and support people who need to open .log, .txt, JSONL, syslog, Apache, and application logs without uploading private data anywhere. Drop a file into Chrome, search with plain text or regex, filter by level, inspect JSON log lines, and keep the whole workflow local on your machine. π
π Why developers love this log viewer
Most log work starts with a simple problem: you have a file, you need to find the failure, and you do not want to wait for a heavy desktop tool or paste production logs into an online site. Log Viewer & Search turns Chrome into a focused log file viewer with the basics done right: fast opening, readable monospace rows, line numbers, level colors, regex search, filter chips, copyable results, and a privacy model you can explain to your security team.
This log viewer chrome tool is built for real debugging sessions. It avoids scary permissions, does not inject scripts into websites, and does not ask for browsing history. The extension opens a bundled viewer tab and uses Chrome file access, drag and drop, and local parsing. Your logs stay in the browser process on your device.
β‘ Everything in the free plan
β Open one .log, .txt, .json, or .jsonl file up to 10 MB
β Drag and drop files or use the native file picker
β Search by keyword, request ID, user ID, stack trace text, host, path, or status code
β Turn on regex search for patterns like timeout|exception|failed
β Filter visible rows by ERROR, WARN, INFO, DEBUG, TRACE, or OTHER
β Auto-detect common log levels from plain text and JSON log fields
β Show line numbers, timestamps, file size, total lines, and visible result count
β Select any line to inspect the full message without losing your place
β Copy filtered lines for a ticket, incident note, or chat handoff
β Load a built-in sample log to learn the interface quickly
β Use a local-first tool with no signup for the core viewer
β Hide timestamp noise when you want to focus on messages
β Convert common ANSI terminal colors into readable highlighted rows
π What Pro unlocks
β¦ Large files: open 100 MB+ logs with chunked reading and virtual scrolling, so the interface stays responsive instead of rendering every row into the DOM.
β¦ Tail follow: re-read a growing local file and keep the newest matching lines in view while an app, build, or server process keeps writing.
β¦ Saved filters: keep recurring searches such as OutOfMemory, 502, payment_failed, user_id, trace_id, or request_id ready for the next session.
β¦ Multi-file workflow: merge related app, worker, proxy, and error logs by timestamp when one file does not tell the whole story.
β¦ Export: save the filtered view as CSV for incident reports, QA evidence, or spreadsheet review.
β¦ JSON log expansion: pretty-print structured JSON log lines so nested fields are readable inside the viewer.
π― Who it is for
This log file viewer is for backend developers checking application errors, frontend engineers reading local build output, DevOps teams triaging deploy issues, QA testers collecting failure evidence, support teams following customer request IDs, and founders debugging production problems without opening a full observability stack. It is also useful on Chromebooks and locked-down machines where installing a native log viewer is slow or impossible.
π οΈ How it works
1. Pin Log Viewer & Search to the Chrome toolbar.
2. Click the extension icon to open the viewer tab.
3. Drop a .log file or choose one with the file picker.
4. Search with text or regex, then filter by log level.
5. Copy the matching lines, inspect JSON entries, export CSV, or use tail follow when the file is still growing.
π‘ Real use cases
β’ Find every ERROR line after a failed deployment.
β’ Search a production request ID across a downloaded application log.
β’ Filter nginx or Apache logs to 500-level responses.
β’ Inspect JSONL logs from Node, Python, Laravel, Rails, Go, or serverless functions.
β’ Keep a growing local log open while reproducing a bug.
β’ Copy only the relevant lines into a Jira, GitHub, Linear, or support ticket.
β’ Review CI build logs without the noise around successful steps.
β’ Check whether failures are warnings, errors, retries, or noisy debug entries.
π Privacy you can verify
Your log content is never uploaded by this extension. Parsing, search, regex filtering, level detection, virtual scrolling, JSON expansion, and export all run locally in Chrome. The extension requests only the storage permission plus the Peak Productivity license host. Storage is used for settings, saved filters, license cache, and anonymous activation counters. The extension does not request tabs, history, downloads, scripting, webRequest, or all-sites access.
π Performance and benchmarks
The viewer reads files in chunks and renders only the visible rows. That matters because a log viewer that freezes on a real file is not useful. Free users can open files up to 10 MB. Pro is designed for 100 MB+ logs through chunked reading, a worker-backed filter index, and virtualized rows that keep the DOM small. Regex work runs off the main UI path so typing a search does not lock the page.
π Why this over the alternatives
β Unlike online log viewers, your logs are not uploaded to a third-party server.
β Unlike a generic text editor, levels, timestamps, filtering, and JSON log entries are part of the workflow.
β Unlike heavyweight observability tools, this is for the file already on your machine.
β Unlike terminal-only workflows, the interface is searchable, visual, and easy to share with non-terminal teammates.
β Unlike extensions that hijack pages, this log viewer opens only when you click it.
π‘οΈ Security
Log Viewer & Search uses Manifest V3, has no remote JavaScript, and ships its logic inside the extension bundle. It does not inject content scripts into websites. It does not need all-sites access. It does not monitor browsing activity. It does not collect website coβ¦