# Symbol Files

Symbol files are critical to getting useful data from your crashes. [Windows](https://docs.bugsplat.com/introduction/getting-started/integrations/desktop/cplusplus), [Breakpad](https://docs.bugsplat.com/introduction/getting-started/integrations/cross-platform/breakpad), [Crashpad](https://docs.bugsplat.com/introduction/getting-started/integrations/cross-platform/crashpad), [MacOS](https://docs.bugsplat.com/introduction/getting-started/integrations/desktop/macos), [Xbox](https://docs.bugsplat.com/introduction/getting-started/integrations/game-development/xbox), [PlayStation](https://docs.bugsplat.com/introduction/getting-started/integrations/game-development/playstation), [Nintendo](https://docs.bugsplat.com/introduction/getting-started/integrations/game-development/nintendo), and some [JavaScript](https://docs.bugsplat.com/introduction/getting-started/integrations/web/javascript) applications require uploading symbol files to generate call stacks that contain function names and line numbers. The symbol upload process can be automated as part of your build. Many of our SDKs require symbols, which can be uploaded and managed via the [Versions](https://app.bugsplat.com/v2/versions) page.

For additional information regarding Symbol files, please visit the [documentation](https://docs.bugsplat.com/introduction/getting-started/integrations) specific to your application's platform.

### What are Symbols?

Symbols are files containing information to map the crash report's call stack to file names and line numbers in source code.

### Using Symbols

[Windows C++](https://docs.bugsplat.com/introduction/getting-started/integrations/desktop/cplusplus) and [.NET](https://docs.bugsplat.com/introduction/getting-started/integrations/desktop/windows-dot-net-framework) symbol files have **.exe**, **.pdb**, and **.dll** extensions.

For [Crashpad](https://docs.bugsplat.com/introduction/getting-started/integrations/cross-platform/crashpad) applications, symbols files contain **.sym** extensions.

For [macOS](https://docs.bugsplat.com/introduction/getting-started/integrations/desktop/macos) applications, symbols files end with a **.dSYM** extension.

For TypeScript and [JavaScript](https://docs.bugsplat.com/introduction/getting-started/integrations/web/javascript) applications, symbols are files with a **.js.map** extension.

Symbol files can be uploaded via [symbol-upload](https://docs.bugsplat.com/education/faq/how-to-upload-symbol-files-with-symbol-upload). Additionally, Crashpad **.sym** files can be [generated automatically](https://docs.bugsplat.com/education/faq/how-to-upload-symbol-files-with-symbol-upload#improving-upload-speeds-1) by invoking symbol-upload with the `-m` argument.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2F3Y0JjG0w6JTuQ0GrIAgr%2Fimage.png?alt=media&#x26;token=49fd18cd-dc4a-4f26-b17f-5121c009d708" alt=""><figcaption><p>BugSplat Versions Page</p></figcaption></figure>

## Additional Resources

{% content-ref url="working-with-symbol-files/source-maps" %}
[source-maps](https://docs.bugsplat.com/introduction/development/working-with-symbol-files/source-maps)
{% endcontent-ref %}

{% content-ref url="working-with-symbol-files/how-to-manually-upload-symbols" %}
[how-to-manually-upload-symbols](https://docs.bugsplat.com/introduction/development/working-with-symbol-files/how-to-manually-upload-symbols)
{% endcontent-ref %}

{% content-ref url="working-with-symbol-files/working-with-windows-symbols-in-bugsplat" %}
[working-with-windows-symbols-in-bugsplat](https://docs.bugsplat.com/introduction/development/working-with-symbol-files/working-with-windows-symbols-in-bugsplat)
{% endcontent-ref %}