1# Troubleshooting
 2
 3## Zed Log
 4
 5Often, a good first place to look when troubleshooting any issue in Zed is the Zed log, which might contain clues about what's going wrong.
 6You can review the most recent 1000 lines of the log by running the {#action zed::OpenLog} command from the command palette (`cmd-shift-p` on macOS or `ctrl-shift-p` on Windows/Linux).
 7If you want to view the full file, you can find it at the respective location on each operating system:
 8
 9- macOS: `~/Library/Logs/Zed/Zed.log`
10- Windows: `C:\Users\YOU\AppData\Local\Zed\logs\Zed.log`
11- Linux: `~/.local/share/zed/logs/Zed.log` or `$XDG_DATA_HOME`
12
13> Note: In some cases, it might be useful to monitor the log live, such as when [developing a Zed extension](https://zed.dev/docs/extensions/developing-extensions).
14> Example: `tail -f ~/Library/Logs/Zed/Zed.log`
15
16The log may contain enough context to help you debug the issue yourself, or you may find specific errors that are useful when filing a [GitHub Issue](https://github.com/zed-industries/zed/issues/new/choose) or when talking to Zed staff in our [Discord server](https://zed.dev/community-links#forums-and-discussions).