File inspection guides

Read File Signatures and Their Offsets

·

A signature compares bytes at specific positions. Its location and any additional rules matter when the same characters occur in different formats.

File Signature Database

Match the DICOM practice header

Enter DICM in Search signatures and expand DICOM Part 10 file. It shows 44 49 43 4D at offset 128.

Choose Load practice header. The tool reads 132 bytes and matches DICM at that offset. The practice header demonstrates the marker and lacks a complete DICOM dataset. Save the JSON to record the matched offsets and reference revision.

Open File Signature DatabaseDICOM Part 10 file preamble and prefixThe National Archives PRONOM DROID signature releases

Check both marker positions for WAVE

Return to database and search .wav. The WAVE entry shows RIFF at offset 0 and WAVE at offset 8. An AVI or WebP container can also start with RIFF. The form code at offset 8 distinguishes these rows.

Check both marker positions for WAVE
ContainerOffset 0Offset 8
WAVERIFFWAVE
AVIRIFFAVI followed by a space
WebPRIFFWEBP

Microsoft RIFF and WAVE form codesGoogle WebP container specification

Keep shared markers as candidate evidence

Search CA FE BA BE in Programs. Its initial four bytes occur in Java class files and Mach-O universal wrappers. Inspect later structures using an appropriate format reader to narrow the candidates.

The reference includes selected fixed-offset patterns from PRONOM DROID V125 and format specifications. Its file matcher reads the first 64 KiB.

The National Archives PRONOM DROID signature releasesJava Virtual Machine class file structureApple Mach-O universal architecture header

Common questions

Can I search a hexadecimal pattern with spaces?

Yes. For example, 44 49 43 4D and 4449434D can both find the DICM bytes.

Does a successful marker match verify every record?

The match covers the listed offsets. A separate reader verifies the complete format rules.

Sources

Put it into practice.

Related guides