> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/guides/working-with-symbol-files.md).

# Symbol Files

Symbol files are critical to getting useful data from your crashes. [Windows](/integrations/desktop/cplusplus.md), [Breakpad](/integrations/desktop/breakpad.md), [Crashpad](/integrations/desktop/crashpad.md), [MacOS](/integrations/desktop/macos.md), [Xbox](/integrations/game-development/xbox.md), [PlayStation](/integrations/game-development/playstation.md), [Nintendo Switch 2](/integrations/game-development/nintendo.md), and some [JavaScript](/integrations/web/javascript.md) 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](/integrations/integrations.md) 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++](/integrations/desktop/cplusplus.md) and [.NET](/integrations/desktop/bugsplat-for-dot-net.md) symbol files have **.exe**, **.pdb**, and **.dll** extensions.

For [Crashpad](/integrations/desktop/crashpad.md) applications, symbols files contain **.sym** extensions.

For [macOS](/integrations/desktop/macos.md) applications, symbols files end with a **.dSYM** extension.

For TypeScript and [JavaScript](/integrations/web/javascript.md) applications, symbols are files with a **.js.map** extension.

Symbol files can be uploaded via [symbol-upload](/guides/working-with-symbol-files/upload-symbols-with-symbol-upload.md). Additionally, Crashpad **.sym** files can be [generated automatically](/guides/working-with-symbol-files/upload-symbols-with-symbol-upload.md#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%2Fgit-blob-260022dba412af8e35feac5150235803dacab8d2%2Fimage.png?alt=media" alt=""><figcaption><p>BugSplat Versions Page</p></figcaption></figure>

## Additional Resources

{% content-ref url="/pages/9CbMAPqdIADsTxgNylgM" %}
[Upload Symbols with symbol-upload](/guides/working-with-symbol-files/upload-symbols-with-symbol-upload.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MeWLeYh35WEExN\_2fue" %}
[How to Manually Upload Symbols](/guides/working-with-symbol-files/how-to-manually-upload-symbols.md)
{% endcontent-ref %}

{% content-ref url="/pages/AW8j5JTuLSk6IkJ00R1y" %}
[Managing Symbol Storage](/guides/working-with-symbol-files/managing-symbol-storage.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mg\_UpA3JIjWidH0gSp6" %}
[Source Maps](/guides/working-with-symbol-files/source-maps.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MeWLPNUInpcGqKnaZDt" %}
[Working with Symbol Files in Windows Environments](/guides/working-with-symbol-files/working-with-windows-symbols-in-bugsplat.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/guides/working-with-symbol-files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.