WIN
Google Chrome - Windows
Google, Inc.Logs
%LOCALAPPDATA%\Google\Chrome\User Data\chrome_debug.log3 log locations · Windows, macOS, Linux
Google, Inc. · Vendor documentation (opens in a new tab)
Google Chrome logs to %LOCALAPPDATA%\Google\Chrome\User Data\chrome_debug.log on Windows.
Google Chrome logs to ~/Library/Application Support/Google/Chrome/chrome_debug.log on macOS.
Google Chrome logs to ~/.config/google-chrome/chrome_debug.log on Linux.
Paths are printed exactly as Google Chrome writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.
%LOCALAPPDATA%\Google\Chrome\User Data\chrome_debug.log~/Library/Application Support/Google/Chrome/chrome_debug.log~/.config/google-chrome/chrome_debug.log--enable-logging --v=1 to the end of the Chrome shortcut Target./Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging --v=1.--enable-logging --v=1.--vmodule=module1=N with a comma-separated list of modules.--enable-logging=stderr (on Windows this misses sandboxed renderer output).CHROME_LOG_FILE environment variable.chrome_debug.log from the Chrome user data directory before restarting Chrome, as each restart overwrites it.chrome://net-export and record a net log.chrome://crashes and note the crash IDs.%TMP%\chrome_installer.log.chrome_installer.log from %systemroot%\SystemTemp or C:\Windows\Temp.updater.log from %LOCALAPPDATA%\Google\GoogleUpdater\ (per user) or %PROGRAMFILES(X86)%\Google\GoogleUpdater\ (system).updater.log from ~/Library/Application Support/Google/GoogleUpdater/ or /Library/Application Support/Google/GoogleUpdater/.