![Kim-Anh Tran](https://web.dev/images/authors/kimanh.jpg) Kim-Anh Tran [X](https://twitter.com/kianhuu) [GitHub](https://github.com/ktran) ![Vaatika Dabra Groth](https://web.dev/images/authors/vaatika.jpg) Vaatika Dabra Groth [X](https://twitter.com/vaatika)

<br />

> [!NOTE]
> **Note:** Interested in helping improve DevTools? Sign up to participate in [Google User Research here](https://google.qualtrics.com/jfe/form/SV_9YbKj35IGoGsDBj?reserved=1&utm_source=Website+feature&Q_Language=en&utm_medium=own_web&utm_campaign=Q4&productTag=chrm&campaignDate=November2020&referral_code=UXFm430458).

![The old and new breakpoint sidebar pane side-by-side.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/the-old-new-breakpoint-s-3626b842be099.png)

If you're on Chrome 111 or later, you might have already noticed that we've changed the design of our breakpoint sidebar. With Chrome 113, the new sidebar entirely replaces the old design. Our goal with the redesign was to **improve the breakpoint workflow** by:

Providing a **better overview** on all breakpoints that are set.
Making common user workflows with breakpoints **easier to access** and **more intuitive** .
Making **cool existing breakpoint features visible**.

This post assumes that you are already familiar with debugging using breakpoints. If you haven't used breakpoints before, head over to [this overview on breakpoints](https://developer.chrome.com/docs/devtools/javascript/breakpoints.md.txt) and learn more about how you can use breakpoints to debug your code.

Now, let's have a look at what the redesign offers, and how you can make use of the new sidebar! Note that the redesign concentrates on making *existing features* more intuitive to use and easier to access, instead of adding new features.

## Pause on exceptions to investigate why your code is throwing an error

![Pause on caught and uncaught exceptions.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/pause-caught-uncaught-e-5772956d73aa6.png)

Does your code throw an exception? Fret not! Chrome DevTools allows you to pause on exceptions to stop execution at the point where your exception is thrown. This can help you to investigate and better understand the circumstances under which your code throws an error. You can choose whether you want to pause on caught exceptions, uncaught exceptions, or both, by checking the corresponding checkboxes in the sidebar.

> [!CAUTION]
> **Caution:** For Node debugging, pausing on caught exceptions with Chrome 113 is only possible if also pausing on uncaught exceptions. This is a dependency that previously existed and needs to be kept for Node LTS compatibility reasons. As soon as Node LTS release 18 is no longer supported, we will also allow independent pausing for Node. Follow [crbug/1382762](https://crbug.com/1382762) for updates.

## Manage your breakpoints: expand relevant breakpoint groups, and collapse others to focus on what's relevant

![Collapse and expand breakpoint groups.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/collapse-expand-breakpoi-4478e29f59418.png)

Breakpoints may be spread across several files. The breakpoint sidebar groups breakpoints according to the file they belong to. Focus on only those that matter for your current debugging session by expanding the relevant breakpoint groups, and collapsing the remaining ones.

> [!IMPORTANT]
> **Key point:** If several files happen to have the same file name, Chrome DevTools will also try to show you a part of the file path next to the file name that can help you to differentiate between files.

## Manage your breakpoints: one click to jump to code, remove, or enable/disable breakpoints

The breakpoint sidebar allows you to accomplish common tasks with one click. Here's an overview of how you can ...

Navigate to the breakpoint location in the Code Editor.
Remove one breakpoint or all breakpoints within a file.
Enable or disable one breakpoint or all breakpoints within a file.

And all this with one click! Of course, these options are also available in the context menu:

### Jump to the breakpoint location by clicking on the breakpoint code snippet

![Jump to the source code location in the code editor.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/jump-the-source-code-loc-276d1ad3dd005.png)

Do you want to check where in the code you have set your breakpoint, and analyze the surrounding code? Just click on the code snippet of a breakpoint within the sidebar, and it will open the code location in the code editor.

### Remove a single breakpoint or all breakpoints within a file by clicking on the remove button

![Remove a single breakpoint or all breakpoints within a file.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/remove-single-breakpoint-d9114a2a9d50a.png)

Hover over a breakpoint or a breakpoint group to reveal a remove button that removes a single or all breakpoints in a file on click.

### Disable a single or all breakpoints within a file

![Enable or disable a single or all breakpoints within a file.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/enable-disable-single-47fb109904226.png)

Check or uncheck the checkbox next to a breakpoint to enable or disable it.

To enable or disable all breakpoints in a file, hover over the breakpoint group and check or uncheck the checkbox that appears next to the file name.

## Make use of these lesser known breakpoint features: conditional breakpoints and logpoints

> [!IMPORTANT]
> **Key term:** If you want to know more about the differences between regular breakpoints, conditional breakpoints, and logpoints, head over to our [documentation on breakpoint types](https://developer.chrome.com/docs/devtools/javascript/breakpoints.md.txt#loc) which explains how you can use these different breakpoint types to debug your code. **TLDR** : conditional breakpoints stop execution only if a *condition* that you specify is true. Logpoints, on the other hand, are the counterpart of using `console.log`, but in Chrome DevTools.

### Edit breakpoint conditions or change your logpoint log by editing a breakpoint

![Edit breakpoint conditions or change logpoint logs.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/edit-breakpoint-condition-6e67003cd664.png)

Edit a breakpoint condition or log by hovering over a breakpoint and clicking the *edit* button that appears. This opens a dialog for changing the breakpoint type and the details of your breakpoint.

Alternatively, select the line of the breakpoint in the code editor and type in <kbd>Control</kbd>+<kbd>Alt</kbd>+<kbd>b</kbd> on Linux and <kbd>Command</kbd>+<kbd>Alt</kbd>+<kbd>b</kbd> on Mac to open the breakpoint edit dialog.

You can also quickly double-check your condition or logpoint log by hovering over the breakpoint in the sidebar:

![View condition or logpoint log.](https://developer.chrome.com/static/blog/breakpoint-ux-redesign/image/view-condition-logpoint-b44c37551c76d.png)

## Conclusion

Our goal behind the redesign of the breakpoint sidebar was to make debugging with breakpoints easier. Most importantly, we aimed to make things more structured, and easier to access and understand. We hope these improvements will help you in your next debugging session!

If you have suggestions for further improvements, let us know by [filing a bug](https://crbug.com/new)!

## Download the preview channels

Consider using the Chrome [Canary](https://www.google.com/chrome/canary/), [Dev](https://www.google.com/chrome/dev/), or [Beta](https://www.google.com/chrome/beta/) as your default development browser. These preview channels give you access to the latest DevTools features, let you test cutting-edge web platform APIs, and help you find issues on your site before your users do!

## Get in touch with the Chrome DevTools team

Use the following options to discuss the new features, updates, or anything else related to DevTools.

- Submit feedback and feature requests to us at [crbug.com](https://crbug.com).
- Report a DevTools issue using the **More options** \> **Help** \> **Report a DevTools issue** in DevTools.
- Tweet at [@ChromeDevTools](https://twitter.com/intent/tweet?text=@ChromeDevTools).
- Leave comments on [What's new in DevTools YouTube videos](https://goo.gle/devtools-youtube) or [DevTools Tips YouTube videos](https://goo.gle/devtools-tips).