Extract printable text from binaries and files to inspect hidden content and debug problems. 07.05.2026 | reading time: 2 min On Linux, the command "strings" pulls sequences of printable characters out of binary blobs and files to reveal human-readable content that can help with debugging, forensics or quick checks. Quick example Create a tiny binary blob and extract readable text with the following session: ```$ printf '\x00hello from strings\x00' > sample.bin $ strings sample.bin hello from strings $ strings -n 4 /bin/ls | head -n 5 GNU /lib /usr GLIBC_2.2.5 ``` Tweak the search Adjust what "strings" returns by changing minimum length and scan behavior, for example: ```$ strings -n 6 sample.bin $ strings -a -o /bin/ls | head $ strings -e l core.dump | head ``` Use `-n` to set minimum match length, `-a` to scan all sections, `-o` to print offsets and `-e` to specify 16-bit encodings. Practical uses Use "strings" to spot configuration fragments in executables, search core dumps for clues, find embedded URLs or credentials, and combine it with `grep` or `awk` to filter results: for example `strings binary | grep -i password`. Complementary tools Pair "strings" with hex viewers and binary inspectors to gain context: dump raw bytes with `xxd`, inspect symbol and section tables with `objdump`, or run `readelf` to locate where the text came from before deeper analysis. Keep digging Mastering small utilities like "strings" speeds up troubleshooting and incident investigation; push further with hex analysis and disassembly and consider formalizing skills with certifications like CompTIA Linux+ or LPIC-1 and intensive exam preparation at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. utilities filesystem security troubleshooting
