Skip to main content

Strings v2.53

By Mark Russinovich

Published: July 4, 2016

 Download Strings
 (150 KB)



Working on NT and Win2K means that executables and object files will many times have embedded UNICODE strings that you cannot easily see with a standard ASCII strings or grep programs. So we decided to roll our own. Strings just scans the file you pass it for UNICODE (or ASCII) strings of a default length of 3 or more UNICODE (or ASCII) characters. Note that it works under Windows 95 as well.


Using Strings

usage: strings [-a] [-f offset] [-b bytes] [-n length] [-o] [-q] [-s] [-u] <file or directory>

Strings takes wild-card expressions for file names, and additional command line parameters are defined as follows:

-aAscii-only search (Unicode and Ascii is default)
-bBytes of file to scan
-fFile offset at which to start scanning.
-oPrint offset in file string was located
-nMinimum string length (default is 3)
-qQuiet (no banner)
-sRecurse subdirectories
-uUnicode-only search (Unicode and Ascii is default)


To search one or more files for the presence of a particular string using strings use a command like this:

strings * | findstr /i TextToSearchFor



Download Strings
(150 KB)




Download Strings
(150 KB)


Runs on:

  • Client: Windows Vista and higher
  • Server: Windows Server 2008 and higher
  • Nano Server: 2016 and higher