Built a file viewer for bioinformatics researchers. Drop any genomics file and see it instantly — no upload, no server, everything runs locally in your browser.
What it does:
- Opens FASTA, FASTQ, VCF, BED, GFF, SAM, CSV/TSV files
- Protein FASTA auto-detected with amino acid property coloring
- FASTQ: quality heatmap, Q30%, per-base quality chart
- VCF: sortable/filterable variant table, Ti/Tv ratio, chromosome density
- DNA motif search with regex patterns
- Genomic coordinate jump (chr1:10000-50000)
- Multi-tab: open several files side by side, diff between them
- Export: CSV, TSV, BED, VCF, HTML
- Screenshots, Coloring, Split views, Histograms, Stats, Compare files etc. More features in help guide.
- BioLang WASM console built in — run data |> filter(|r| r.gc > 0.5) directly on your data
- Dark/light theme, keyboard shortcuts, large file streaming
Privacy: 100% client-side. Files never leave your machine. No analytics, no tracking, no account.
All parsing is done in JavaScript + WebAssembly using the BioLang runtime compiled to WASM.
Links:
- Chrome and Brave extension: https://chromewebstore.google.com/detail/biopeek/dpeahehokmlmjabfladeafoidnfaodai
- Firefox: https://addons.mozilla.org/en-US/firefox/addon/biopeek/
- Edge: BioPeek - Microsoft Edge Addons
- Web app (no install needed): https://lang.bio/viewer.html
- Source: https://github.com/oriclabs/biolang
- Full feature guide: https://lang.bio/docs/tools/viewer-help.html (for extension help guide , click on BioPeek tool, click help)
Why BioPeek helps where the tooling doesn't reach
Most bioinformatics tools are Linux-first. On Windows the standard answer is "install WSL" — which is fine until it isn't.
Nothing to install. samtools, bcftools and bedtools mean WSL, Docker or Conda before you can open a single file. BioPeek needs a browser.
No filesystem crossover. Reading Windows files from WSL over /mnt/c is slow and the paths are a constant translation tax. BioPeek opens the file where it already is.
The data never leaves the machine. The usual Windows workaround is some online viewer. That's an upload — often unacceptable for patient or pre-publication data. BioPeek parses locally; as an extension it works with no network at all.
Format-aware, not just a text view. FASTA, FASTQ, VCF, BED, GFF and CSV are recognised and summarised (read quality, Q30, per-record stats), so you get the shape of the file without writing a pipeline first.
Triage before commitment. "Is this file what I think it is, and did the transfer complete?" answered in seconds, rather than after setting up an environment to find out the header is wrong.
Same engine as the CLI. It runs the BioLang WebAssembly build, so what you see matches what BioLang computes later — not a second implementation that might disagree.
Locked-down machines. Where WSL, admin rights or Docker aren't available — shared lab PCs, hospital IT, teaching labs — a browser usually still is.
Still early. BioPeek is young and you will find rough edges: formats it parses more strictly than the tool that wrote them, files large enough to strain browser memory, edge cases nobody has hit yet. Please report what breaks, with the file shape if you can share it — https://github.com/oriclabs/biolang/issues
What it isn't: a replacement for samtools on real workloads. It's bounded by browser memory and aimed at inspection, triage and teaching. For genome-scale processing you still want the CLI — on Linux, or on Windows via WSL
Built on Rust libraries, not from scratch
The file-format layer isn't mine and shouldn't be.
noodles does the heavy lifting for FASTA, FASTQ, SAM, BAM, BGZF and CSI. It's the established Rust bioinformatics I/O library and it's maintained by people who know those specs far better than I do.
flate2, bzip2, zstd for compression; wasm-bindgen for the browser build.