.DUMP

DUMP File

Breakpad symbol (library symbols) file
Ask a question
QUICK ANSWER

A .dump file listed here is a Breakpad library symbols file - plain-text data mapping machine-code addresses to function names and source lines. Developers feed it into Google's Breakpad tools alongside a crash report to get a readable stack trace. Note that .dump is a generic extension also used for memory dumps and database exports, which are unrelated.

Developer: Google (Breakpad / Crashpad project) Category: Developer Files Open standard MIME: text/plain
OPENS ON Windows macOS Linux
Related: .DO · .MD · .HEX · .XSD

On this page

19k+ extensions indexed
Last reviewed Aug 1, 2026

Not sure what your file is?

Drop any file into our identifier - we read just the first bytes to name the format.

Identify a file

What is the DUMP file format?

The .dump extension is used by symbol files created by Google Breakpad, an open-source crash-reporting library used by various software, including Mozilla Firefox. Rather than recording crash details themselves, .dump files are plain-text debug-symbol tables generated by the dump_syms tool from a binary's native debug data (Windows PDB files, ELF DWARF, or macOS DWARF/STABS). They map raw machine-code addresses to function names, source-file paths and line numbers.

.dump files are produced in advance and stored on a symbol server or local directory, not generated when a program crashes. When a crash does occur, the companion tool minidump_stackwalk reads the .dump symbol file together with a minidump crash report to produce a human-readable stack trace. The resulting symbolicated trace, along with the crash report, can be sent to software developers in order for them to determine and address the errors causing the program to crash.

A Breakpad symbol file is line-oriented ASCII text. The first line is always a MODULE record - for example MODULE Linux x86_64 <build-id> libfoo.so - identifying the OS, CPU architecture, a unique build ID and the library or executable name. Subsequent records (FILE, FUNC, PUBLIC, STACK) carry the rest of the symbol mapping; later format revisions add INLINE and INLINE_ORIGIN records, and readers are designed to tolerate unknown record types. Files range from tens of kilobytes to hundreds of megabytes depending on the size of the library being symbolicated.

Because .dump symbol files are plain ASCII, they can be inspected in any text editor such as Notepad++ or VS Code, or processed programmatically by Sentry CLI and the symbolic library, which also support the same Breakpad symbol format.

Security & safety

RISK: LOW

A Breakpad symbol file is plain text with no executable content, so it's safe to open. The only real concern is that symbol files expose internal function names and source paths of a program (mild information disclosure), so vendors usually keep them on private symbol servers. Because '.dump' is also used for memory dumps and database exports, verify what a given file actually is before assuming it's harmless - a raw memory dump can contain sensitive data.

Format details

in a nutshell
FULL NAMEBreakpad symbol (library symbols) fileaka Breakpad symbol file, Library symbols file
DEVELOPERGoogle (Breakpad / Crashpad project)since 2007 (Google Breakpad open-sourced; symbol-file format dates from that era)
MIME TYPEtext/plain
TYPEPlain-text debug-symbol table for crash-stack symbolication
STANDARDOpen · royalty-free
This extension is also used by…
  • Memory / crash dump file - A raw process or kernel memory dump (e.g. core dump, Windows .dmp) - binary, opened in a debugger; unrelated to text symbol files.
  • Database / SQL dump - A text export of a database produced by tools like mysqldump/pg_dump; replayed back into the database, not a symbol table.
  • Wireshark / packet capture or generic data dump - Various tools write a '.dump' of raw captured or exported data; format depends entirely on the producing tool.

Programs that open DUMP files

Windows3 apps
Text editor (Notepad++, VS Code) Open-source Open the file to read the MODULE/FUNC/PUBLIC records - it's plain text. Useful to confirm it's a Breakpad symbol file and check the debug id.
Breakpad tools (minidump_stackwalk / dump_syms) Open-source Use minidump_stackwalk with a minidump and the symbol files to produce a symbolicated stack trace; dump_syms generates these files. (BreakPad in db.)
Sentry CLI / symbolic Open-source Use sentry-cli / the 'symbolic' library to validate and process Breakpad symbol files for crash symbolication.
macOS2 apps
Breakpad tools (minidump_stackwalk / dump_syms) Open-source Build Breakpad and run dump_syms on a binary or minidump_stackwalk to symbolicate; symbols are the same text format.
Text editor (VS Code / BBEdit) Free Open the plain-text symbol file to inspect its records.
Linux2 apps
Breakpad tools (minidump_stackwalk / dump_syms) Open-source dump_syms generates the file from ELF/DWARF; minidump_stackwalk consumes it with a minidump to print a stack trace.
Any text editor / less Open-source It's ASCII text - open with any editor or 'less' to read the records.

Technical details

deep spec
Format typePlain-text debug-symbol table; line-oriented ASCII records mapping machine-code addresses to function names and source locations
MIME typetext/plain (also seen as application/octet-stream in generic transfer contexts)
File header / magicNo binary magic bytes; first line is always a MODULE record: MODULE <os> <arch> <build-id> <name>
Text encodingASCII; lines delimited per host platform (LF on Unix, CRLF on Windows)
ContainerPlain text - no binary wrapper, no embedded sections or chunks
CompressionNone built-in; files may be stored gzip-compressed externally on symbol servers
Typical file sizeTens of KB to hundreds of MB - scales with the number of functions and source lines in the symbolicated binary
Record typesMODULE (header), FILE (source path list), FUNC (function address ranges), PUBLIC (exported symbols), line-number records, STACK (frame-unwinding), INLINE, INLINE_ORIGIN
Build ID / match keyThe MODULE record embeds a debug build ID (hash) used to pair the symbol file with the exact binary or minidump
Producer tooldump_syms (Breakpad/Crashpad) - extracts symbol data from Windows PDB, ELF DWARF or macOS DWARF/STABS debug info
Consumer toolsminidump_stackwalk (Breakpad), Sentry CLI, symbolic library (Rust/Python) - all read this format to symbolicate crash stack traces
Platform supportWindows, macOS, Linux, Android - Breakpad and Crashpad generate and consume .dump symbol files on all four platforms
Format extensibilityAdditive keyword-record design; parsers skip unrecognised record types, allowing INLINE and INLINE_ORIGIN records to be added without breaking older tools
Source debug formats readWindows PDB (.pdb), ELF DWARF (.so / .elf), macOS DWARF and STABS (.dSYM / .dylib) - dump_syms converts all of these into the unified .dump symbol format
Released2007 (Google Breakpad open-sourced; symbol-file format dates from that era)
Latest versionBreakpad symbol format additively extended (INLINE/INLINE_ORIGIN records added in later revisions); no formal version number
Open standardYes · royalty-free
Specificationgithub.com

DUMP conversions

Community Q&A

asked by users
Ask a quick question
Get help from people who work with DUMP files. Be specific - include your system and software version.
No account needed · answers usually within a day

No questions yet - be the first to ask about DUMP files.

Frequently asked questions

What is a .dump file?
In the sense listed here, it's a Breakpad library SYMBOLS file - a plain-text map of function names and source lines used to symbolicate crash reports. The extension is generic, though: it's also used for memory dumps and database/SQL exports.
How do I open a Breakpad symbol (.dump) file?
It's ASCII text - open it in any editor to read its MODULE/FUNC/PUBLIC records. To actually use it, feed it with a minidump to Breakpad's minidump_stackwalk to produce a stack trace.
What's the difference between a .dump symbol file and a .dmp crash dump?
The .dmp minidump is the binary snapshot of the crash (registers/stack); the symbol file is the text that maps addresses to function names. You combine them to get a readable crash trace.
Why does my crash trace show hex addresses instead of function names?
The symbol file is missing or doesn't match the binary. Generate symbols with dump_syms from the exact build (the MODULE debug-id must match) and point the processor at them.
Is my .dump a symbols file, a memory dump, or a database export?
Check the first bytes: a Breakpad symbol file starts with a text 'MODULE …' line; a database dump is readable SQL/text; a memory/core dump is binary and needs a debugger. The extension alone doesn't tell you.

References

1Google Breakpad - Symbol file formatgithub.com
2Google Breakpad - project repositorygithub.com

Keep exploring

across the database

Top extensions this week

1.AQQAQQ Instant Messenger File
2.CRDOWNLOADChrome Partial Download File
3.MDMarkdown Document
4.BINCD/DVD Disc Image (BIN/CUE)
5.NOMEDIAAndroid No-Media Marker File
6.PARTPartial Download File
7.RPMSGRestricted Permission Message
8.EXEWindows Executable (Portable Executable)
9.AVIFAV1 Image File Format (AVIF)
10.DBSQLite Database File

Related extensions

.DOStata Do-File
.MDMarkdown Document
.HEXIntel HEX File
.XSDXML Schema Definition
.MAPSource Map (JavaScript / CSS)
.CONFIGConfiguration File

Free file tools

An in-browser file identifier and image converter - everything runs on your device.

Open the toolbox

Browse file extensions A-Z