Use IntelliJ IDEA itself first when you need the IDE log for a bug, freeze, plugin error, indexing problem, or crash. JetBrains Toolbox is useful for managing installed IDE versions and checking Toolbox’s own update or install logs, but it is not the fastest route to the active idea.log file. If IntelliJ IDEA opens, go straight to Help > Show Log in Explorer/Finder/File Manager. If it does not open, use the operating system log folder or check Toolbox to confirm which IDE version you installed.
TL;DR: IntelliJ IDEA is the better tool for finding the current IDE log because it opens the exact folder used by the running instance. JetBrains Toolbox helps when you manage multiple IDE versions, rollback builds, or troubleshoot installation and update failures. For example, in a 25-developer team with both Stable and EAP builds installed, Toolbox can cut version confusion sharply, but IntelliJ still gets you to idea.log in about three clicks. Expect the fastest path to be Help > Show Log, not hunting through folders by hand.
Why IntelliJ IDEA Logs Matter
The IntelliJ IDEA log is where the IDE writes what it was doing before something went wrong. It records plugin errors, indexing events, memory warnings, Git integration problems, Gradle sync failures, internal exceptions, startup issues, and UI freezes. The main file is usually called idea.log.
When JetBrains support, your team lead, or a plugin author asks for logs, they usually mean this file. Not a screenshot. Not a vague “it crashed again.” The log gives names, timestamps, stack traces, and build numbers. That saves a lot of guesswork.
The annoying part is that there are two JetBrains tools in the conversation: IntelliJ IDEA and JetBrains Toolbox. They overlap just enough to confuse people. Honestly, it feels like a small tax on your time when all you wanted was one file.
Best Method: Find Logs from Inside IntelliJ IDEA
If IntelliJ IDEA starts, use the built-in menu. It knows the exact log directory for the current build, current user, and current settings path.
- Open IntelliJ IDEA.
- Click Help.
- Select Show Log in Explorer on Windows.
- Select Show Log in Finder on macOS.
- Select Show Log in File Manager on Linux.
- Open idea.log.
This method is the cleanest because it avoids guessing the product version folder. That matters if you have IntelliJ IDEA 2023.3, 2024.1, and 2024.2 installed at the same time. The log you need belongs to the IDE instance that is actually running.
You may also see older rotated logs such as idea.log.1 or compressed archives. Keep them if the issue happened earlier. If the bug happened five minutes ago, start with the plain idea.log file.
When to Use “Collect Logs and Diagnostic Data”
For support cases, IntelliJ IDEA has an even better option: Help > Collect Logs and Diagnostic Data. This creates an archive with useful troubleshooting data. It may include logs, thread dumps, system information, and other diagnostics.
Use this when:
- The IDE freezes or becomes slow.
- A plugin throws repeated internal errors.
- Indexing never finishes.
- A JetBrains support engineer asks for a full diagnostic bundle.
- You cannot tell which log file matters.
Before sharing the archive, scan it if your project names, paths, usernames, or private server URLs are sensitive. Logs are technical files, but they can still expose local paths and environment details.
Default IntelliJ IDEA Log Locations
If IntelliJ IDEA will not launch, use the default log folders. The exact folder name changes by product version. Replace 2024.2 with your installed version if needed.
| System | Typical IntelliJ IDEA log path |
|---|---|
| Windows | %LOCALAPPDATA%\JetBrains\IntelliJIdea2024.2\log |
| macOS | ~/Library/Logs/JetBrains/IntelliJIdea2024.2 |
| Linux | ~/.cache/JetBrains/IntelliJIdea2024.2/log |
The catch is that version folders pile up. After a few upgrades, you may see several nearly identical directories. Check the file timestamp. The newest idea.log is often the one you need.
Where JetBrains Toolbox Fits In
JetBrains Toolbox is not just a launcher. It installs, updates, removes, and rolls back JetBrains IDEs. It also helps you see which edition and version you are using. That is useful when a teammate says, “It works on my IntelliJ,” and then you find out they are on a different build.
Toolbox is most helpful for logs in three cases:
- Installation failed: IntelliJ IDEA never installed correctly, so there is no useful IDE log yet.
- Update failed: Toolbox downloaded or applied an update poorly.
- Multiple IDE builds exist: You need to confirm which IntelliJ version should have produced the log.
Toolbox has its own logs. These are about Toolbox activity, not your coding session inside IntelliJ IDEA. They can show download failures, update errors, permission problems, and startup issues related to the Toolbox app.
Typical Toolbox log locations are:
- Windows:
%LOCALAPPDATA%\JetBrains\Toolbox\logs - macOS:
~/Library/Logs/JetBrains/Toolbox - Linux:
~/.local/share/JetBrains/Toolbox/logs
If IntelliJ crashes during coding, Toolbox logs are usually the wrong files. If IntelliJ will not install, update, or launch from Toolbox, then Toolbox logs suddenly matter.
IntelliJ IDEA vs JetBrains Toolbox: Quick Comparison
| Task | Use IntelliJ IDEA | Use JetBrains Toolbox |
|---|---|---|
| Find current idea.log | Best choice | Limited help |
| Collect diagnostic bundle | Best choice | No |
| Check installed IDE versions | Possible | Best choice |
| Troubleshoot failed update | Sometimes | Best choice |
| Rollback to older IDE build | No | Best choice |
The simple rule: IDE behavior problems belong to IntelliJ logs. Installation and update problems belong to Toolbox logs.
Managing Logs Without Making a Mess
Logs are safe to copy. They are usually safe to delete while the IDE is closed, though keeping recent logs is smart when a bug is still unresolved. IntelliJ IDEA will create fresh log files the next time it starts.
A clean workflow looks like this:
- Reproduce the problem once.
- Immediately open Help > Show Log.
- Copy idea.log to your desktop.
- Rename it with the issue date, such as
idea-log-gradle-sync-2024-09-18.log. - Attach it to your support ticket or internal bug report.
Do not paste a 20,000-line log into chat unless someone asks for a short excerpt. Attach the file. It is easier to search, and it preserves formatting.
Practical Troubleshooting Tips
- Check timestamps first. A stale log wastes time.
- Search for “ERROR”. It is often the fastest clue.
- Search for plugin names. Many IDE issues come from third-party plugins.
- Compare builds. Toolbox can confirm if the issue started after an update.
- Keep one failed run clean. Restart IntelliJ, reproduce the bug, then collect logs.
It drives me crazy that a simple plugin crash can hide inside thousands of normal startup lines. Still, the log usually has the answer. The key is grabbing the right one before it gets rotated or buried under newer sessions.
Final Recommendation
Use IntelliJ IDEA to find and package IDE logs. Use JetBrains Toolbox to manage installations, confirm versions, handle rollbacks, and inspect Toolbox update logs. They solve different problems, even though they sit close together in the JetBrains ecosystem.
If the IDE opens, do not overthink it: Help > Show Log. If the IDE does not open, check the default log folder and then inspect Toolbox only if installation, launching, or updating is part of the failure. That split saves minutes every time, and on a broken workday, minutes feel very expensive.