Torrent file viewer: what a .torrent will download, before you open it
Drop a .torrent file to see every file it will put on your disk, with sizes, before a torrent client touches it. You also get the info hash (SHA-1, and SHA-256 for v2 torrents), a magnet link to copy, the trackers and web seeds, the private flag, who made it and when, and a warning for programs, double extensions and "video" releases with no video in them.
The file is read on your device. Nothing is uploaded, and no tracker, peer or DHT node is contacted.
What it shows
- Every file in a folder tree, with each folder's file count and total size, and the whole list as a CSV (path, size in bytes, readable size, warnings) for a spreadsheet. Padding files that BEP 47 torrents add to align pieces are counted but left out of the list, because clients never write them to disk.
- The info hash, the torrent's ID: the SHA-1 of the file's
infosection for v1 torrents and the SHA-256 for v2 (BEP 52); a hybrid has both. It is computed from the exact bytes in the file, so it matches what your client and any tracker show. - A magnet link with the hash or hashes, the name, the total size, every tracker and every web seed, and a button to copy it. The page never opens it.
- Trackers in their tiers (BEP 12), web seeds (BEP 19 HTTP mirrors), the private flag (BEP 27: no DHT, no peer exchange), the piece size and count, the client that made it and when, the comment, and a private tracker's source tag.
- Hybrid checks: a hybrid torrent carries a v1 file list and a v2 file tree. If they disagree, a v1 client and a v2 client download different files from the same torrent; the page says so and lists both.
The warnings, and what they mean
| Warning | Raised for | Why it matters |
|---|---|---|
| Program or script | .exe .scr .bat .cmd .msi .js .vbs .lnk, and .pif .ps1 .vbe .jse .wsf .hta .cpl | On Windows, opening any of these runs code with your permissions. Normal in a software download; a red flag in a film, album or e-book. |
| Double extension | a name such as Film.2024.1080p.mp4.exe or song.mp3 .scr | Windows hides known extensions by default, so the file shows as Film.2024.1080p.mp4 with a video-like icon chosen by its maker. |
| Disguised name | an invisible right-to-left override (U+202E) or other bidi control in a name | Movie[U+202E]4pm.exe displays as Movieexe.mp4: the letters after the control are shown backwards. |
| Unsafe path | .., an empty part, a drive letter or a slash inside a name | Written as is, the file would land outside your download folder. Current clients refuse or rename these. |
| No video in a video release | a torrent named with 1080p, 720p, 2160p, x264, x265, HEVC, WEB-DL, BluRay, HDTV or S01E02 that holds no .mkv, .mp4, .avi, .mov, .wmv, .webm, .ts, .m2ts, .mpg, .vob or .iso | The classic fake: a "new film" that is really a password-protected archive, a "codec" installer or a link to a "player" site. |
A torrent with no warning is not proven safe: an .mkv can still be the wrong film, and a .pdf or .docx can carry its own exploit. The warnings catch the cheap tricks that make up most fakes.
A worked example: Arch Linux's install image
The torrent archlinux-2026.09.01-x86_64.iso.torrent from archlinux.org is 87,307 bytes. It opens as one file, archlinux-2026.09.01-x86_64.iso, of 1,608,286,208 bytes (1.50 GB), split into 3,068 pieces of 512 KB. Its v1 info hash is f45add9d1a5185d8588df7dd6cd89993dd0174fa, the same hash as the magnet link on Arch's download page, which is how you know the file you have is the one Arch published. It lists no tracker at all: clients find peers through the DHT, and through 468 web seeds, which are Arch's ordinary HTTPS mirrors. It was made by mktorrent 1.1 on 2026-09-01 at 17:12 UTC, and raises no warning.
Most of those 87 KB are the piece hashes: 3,068 SHA-1 hashes of 20 bytes each, 61,360 bytes, which is why a .torrent for a large file is still small. A v2 torrent keeps per-file SHA-256 hash trees instead, so the same file gets a v2 hash that has nothing in common with its v1 hash.
What this cannot do
- It does not download anything. It reads only the .torrent file you give it: the list of files and their hashes. The files themselves never come near this page.
- It does not contact trackers or check peers. No tracker, DHT node, peer or web seed is asked anything, so it cannot tell you how many seeders a torrent has, whether it is still alive, or whether a web seed still answers.
- It cannot tell whether the content is legal or safe. Names and sizes are whatever the torrent's maker typed. A file called
episode.mkvcan hold anything, and many legal downloads (installers, Linux tools) rightly contain programs. - It does not check the pieces. Verifying downloaded data against the piece hashes needs the data; your torrent client does that as it downloads.
- Magnet links are not read. A magnet link has no file list in it: a client gets the list from peers. Paste a magnet into your client and save the .torrent it fetches, then drop that file here.