# Symbol Files

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

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

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

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

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

<figure><img src="/files/Uf4KBy99VjAvPFCyZjcC" alt=""><figcaption><p>BugSplat Versions Page</p></figcaption></figure>

## Additional Resources

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

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

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bugsplat.com/introduction/development/working-with-symbol-files.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.