A ZIP, read from the end
The archive keeps its index at the end, so 67 KB of a 40 MB file lists everything inside it.
Browser extension Chrome, Edge, Firefox
Right-click a file link, choose Open with Foretaste, and it opens. The bytes go from that website to your browser and are read there. Nothing is uploaded to us, because there is nowhere to upload it to.
A link called attachment?id=18392. A 300 MB archive that might hold the slides
or might hold last year's. A spreadsheet from someone you half-know. You cannot tell from
the outside, so you download it, wait, find out, and now it is in your downloads folder
whether you wanted it or not.
Or you do not download it, and you never find out. On a work laptop or a shared machine that is often the sensible choice, and it is still the wrong outcome.
Allow Foretaste on the site you are reading.
It arrives with access to no websites at all and asks for none. You grant one site at a time, from a button, and you can withdraw it just as easily.
Right-click the file link and choose "Open with Foretaste".
Or click the small marker Foretaste puts beside file links on pages you have allowed. Either way it is one action — no dialog asking what you meant.
Look at the file, then decide.
It opens in a panel over the page, or in a new tab if you prefer that. Save it to disk or close it and carry on reading.
104 file extensions, grouped by what you get on the screen. The list below is generated from the extension's own detection table, so it cannot drift from what the code does.
.pdf .docx .odt .ott .pptx .odp .otp
.xlsx .xls .ods .ots .csv .tsv
.zip .tar .gz .tgz .7z .rar .bz2 .tbz2 .tbz .xz .txz .lzma .zst .cab .iso .cpio .ar .lzh
.txt .log .md .markdown .json .jsonl .ndjson .xml .yaml .yml .ini .conf .cfg .env .sql .js .ts .jsx .tsx .css .scss .html .htm .py .java .c .cpp .h .hpp .sh .bash .ps1 .rs .go .php .rb .sqlite .sqlite3 .db .parquet
.jpg .jpeg .png .gif .webp .avif .bmp .ico .svg .heic .heif .mp3 .wav .m4a .ogg .flac .mp4 .webm .mov .m4v
.epub .ttf .otf .woff .woff2 .srt .vtt .ass .ssa
.ics .ifb .vcf .vcard
Worth knowing before you install something rather than after. None of this is a roadmap item being coy — it is what the code does today.
.tar comes back in a single
request.
Every parser runs inside the extension, on your machine. Foretaste requests the file from the website it already lives on — the same request your browser would make if you clicked the link — and reads it there. No file, no file name and no page address is sent to a Foretaste server.
There is no analytics, no telemetry and no crash reporting, and a check in the build script
fails the release if any network call other than fetch, or any hard-coded
address outside a small allowlist, appears in the output.
Exactly what Foretaste can and cannot see, including every request it is capable of making.
No format is behind the plan. Every file Foretaste can read, it reads for everybody — and saving to disk is free on every screen, including the ones where the preview failed.
Pro is depth on top: search every file inside an archive without unpacking it, filter a million-row table down to the rows you wanted, take the pictures out of a document, read rows out of a database, compare two files or two archives.
And it collects: every value of a field, across the whole file, as a list with how often each appeared. The file writes the menu. An XML document offers its own tags, a JSON file its own keys, a log its own fields, a CSV its own columns — so pulling every name out of an archive listing is a choice from a dropdown rather than a regular expression you had to work out first. What Pro costs.
The store listings are not published yet. Each page below tells you the state of that browser's build honestly, and what Foretaste asks your browser for.
Desktop browsers. Chrome extensions do not run on Chrome for Android — that is Google's limitation, not ours — and Firefox for Android is not claimed until it has been tested on one.