tailspin
A command-line log file highlighter that colors numbers, dates, IP addresses, UUIDs, URLs and other patterns in logs of any format.
Tested on Linux
Use it
Linux x86_64
You need first
- System packages:
less
Download tailspin 7.0.0 x86_64 musl release tarball from GitHub and install tspin into ~/.local/bin
mkdir -p ~/.local/bin /tmp/ts && curl -fsSL -o /tmp/ts/ts.tar.gz https://github.com/bensadeh/tailspin/releases/download/7.0.0/tailspin-x86_64-unknown-linux-musl.tar.gz && tar -xzf /tmp/ts/ts.tar.gz -C /tmp/ts && install -m 755 "$(find /tmp/ts -name tspin -type f | head -n1)" ~/.local/bin/tspin
Check that it works
tspin --versionThe output should contain “tspin 7.0.0”.
First thing to try
echo "hello null" | tspinRun tspin <file> to open a log file with highlighting.
What it does
- View or follow log files of any formatTested
How to use it
- Run
tspin <file> --printto print the log file with highlighting to the terminal.
- Run
- Highlight numbers, dates, IPs, UUIDs and URLsNot tested
- Customize highlight groupsNot tested
- Highlight your own keywords from the command lineNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 1 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- highlight live Kubernetes pod logs
- view and follow a log file with highlighting in less
- colorize journalctl output
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version tspin 7.0.0
Differences the test machine hit
- README: Install via cargo install tailspin or package managers (brew, pacman, nix, pkgin, pkg, scoop)
In the test: No Rust toolchain or listed package manager in the box; used the prebuilt x86_64-unknown-linux-musl tarball from the GitHub 7.0.0 release, which the README does not mention - README: Highlights are shown in colour
In the test: The tool output contains ANSI escape codes; this log view hides them, so the checks piped the output through cat -v (with pipefail) to show the colours