What this does
This tool scans a file byte by byte and reports every run of printable characters at least as long as your chosen minimum — exactly what the classic Unix strings -n <N> command does for ASCII text, plus an equivalent pass for UTF-16LE (the two-bytes-per-character encoding Windows binaries commonly use for wide string literals and resources, matching strings -e l -n <N>).
Why byte offsets matter
Each match is reported with both its decimal and hexadecimal byte offset in the file. If you are cross-referencing a disassembler, a hex editor, or a section table (see the ELF, PE and Mach-O inspectors on this site), the offset tells you exactly where in the file the string lives.
Controls
- Minimum length: shorter values surface more noise (three printable bytes in a row happens by chance in real binary data); longer values miss short-but-meaningful strings like error codes or format specifiers. 4-8 is a reasonable default, matching common
stringsusage. - UTF-16LE toggle: turn this off if you only care about ASCII/UTF-8 content — it roughly halves the scan's noise on files with a lot of non-text binary data.
- Filter: a live, case-insensitive substring search over the already-extracted strings — useful for finding a specific URL, error message, version string, or library name inside a large binary.
What it's good for
Finding embedded URLs, file paths, error messages, version strings, hardcoded credentials left in a build by mistake, or simply getting a first read on what an unfamiliar binary does before reaching for a disassembler.
Limitations
This mirrors strings' byte-printable-run detection for ASCII and UTF-16LE only — it does not attempt UTF-8 multi-byte sequences, UTF-16BE, or other encodings.
Privacy
Everything runs locally in your browser. The file you choose is never uploaded anywhere.
Tiny Online Tools







