Is my file uploaded?
No. The hex viewer reads only the bytes it shows, straight from the file on your device, inside your browser tab. Nothing is uploaded or stored.
See the raw bytes of any file, side by side as hex and text. Jump to an offset, read the value under the cursor as an integer, float, or timestamp, search for text or byte patterns, and pull out every readable string. Only the bytes on screen are read, so even very large files open instantly, and nothing leaves your browser.
Loading the file inspector.
You do not have to take our word for it. Browser developer tools list every request a page makes, so you can watch 2file work and confirm that your file is never sent anywhere. The check takes about a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.A file you open is read into this tab's memory, parsed by code that is already on the page, and, for the metadata remover, handed back to you as a new download. It is never uploaded, never stored in the browser, and gone when you close the tab. The only other request the site can make is the feedback form, and only when you submit it.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so even a bug could not send your file elsewhere.
A hex viewer shows the contents of a file as numbers instead of interpreting them. Each byte is written as two hexadecimal digits, from 00 to FF, sixteen bytes to a row, with the offset of the row on the left and the same bytes as text on the right. Readable characters show as themselves and everything else as a dot.
It is the tool people reach for when a file will not open, when they need to check a signature or a header field, when they suspect something is hidden inside a file, or when they are learning how a format is built. Because it does not depend on any format, it works on every file.
The search reads the file in chunks of a few megabytes, so it works on large files and shows its progress, and you can stop it at any time. It lists up to 10,000 matches; Previous and Next jump the view to each one and highlight it.
Strings are runs of readable characters inside a binary file. Pulling them out is one of the quickest ways to learn about an unknown file: a program's strings often include error messages, file paths, web addresses, and the names of the libraries it uses, and a document's strings can reveal the software and user names that created it.
The strings list finds runs of plain ASCII text and of UTF-16 text, with a minimum length you choose, and shows the offset of each one. Click an offset to jump to it in the hex view, filter the list, or download every string with its offset as a text file.
Offsets can be typed as decimal numbers, as hexadecimal with a 0x prefix, or as a percentage of the file size.
Every tool is on the 2file home page. Part of the 2suite.io privacy-first ecosystem.
No. The hex viewer reads only the bytes it shows, straight from the file on your device, inside your browser tab. Nothing is uploaded or stored.
Any size your browser can open. The view, the search, and the strings list read the file in slices, so the whole file is never loaded into memory at once.
No. 2file is an inspector: the hex viewer is read-only, so it can never damage a file.
The selected byte has a blue outline, search matches are shaded amber, the current match is a stronger amber, and zero bytes are dimmed.
Choose Text (UTF-16) in the search, or keep Include UTF-16 strings switched on in the strings list. Windows often stores text with two bytes per character, which a plain search does not match.
No. File hashes are in 2toolbox Hash, and ZIP and GZIP tools are in 2toolbox. Both are sister apps that also run in the browser.