Debugging icons for React.

244 icons across 68 libraries carry the debugging tag. Counting each design once (a set's outline and filled wallet are one design), that's 179, which is what the wall shows.

debugging is a tag: a word for what an icon shows or is for. It is set from each icon's name, its keywords and what it shows, the same way for every library, so a debugging icon from Lucide and one from Tabler land on this page even when the sets name them differently.

The designs most libraries draw for debugging are bug, sentry, insomnia, debug, insomnia wordmark and log. Search the wall to find a specific one.

The tags that most often share icons with debugging are testing, snapshot, troubleshooting, issue and error. They are listed on this page; open one to widen or narrow your search.

244 icons carry the tag but only 179 designs: many sets draw a design in several styles, like outline, filled and duotone, and each style is its own icon. The wall shows one icon per design for each library.

Solar has the most, 9 designs, then SVG Logos (8) and Google Material Icons (7). Among the popular sets: Lucide has 4, Material Symbols has 6, Tabler Icons has 3 and Simple Icons has 5. Pick one above the wall to see only its icons.

68 libraries draw debugging icons, each in its own style. The page shows the first ones as rows of how each set draws it, and a picker above the wall narrows it to one library, so you can see debugging icons that match the rest of your project.

Lucide has 4 designs for debugging, in the line style shadcn/ui ships with. Tabler and Phosphor, in a similar style, are the other sets to check in the picker above the wall.

Open a debugging icon, then copy it as a typed React component or as SVG for Vue, Svelte, Angular or any design tool, or download it as SVG or PNG. Signed in, you can install it with one shadcn CLI command.

Open a debugging icon, then Get icon, then Copy as code: React, Vue, Svelte, Angular, Solid or Preact. Each is one self-contained component with the SVG inside, so only the icons you import reach your bundle.

Open the icon, choose Get icon, then Install with shadcn CLI, and run the command. It adds one file to components/icons, ready to import. It needs a free account.

Yes. On an icon's page, Customize sets the color, size, stroke, rotation and padding, and every copy and download uses them. 21 libraries here are multicolor and keep their own colors.

Single-color icons are drawn in currentColor, so a Tailwind class recolors them: text-primary, text-muted-foreground or any theme token. Size one with size-5 or size-6.

With a visible label beside it, a debugging icon is decoration: add aria-hidden="true". Alone, as in an icon button, name the button for what it does ("Pay", not "credit card") with aria-label. The installed component passes every SVG prop through.

Pair it with text when its meaning could be read two ways: icons for debugging differ from set to set, and a label removes the doubt. Single-color icons use currentColor, so they follow your text color and keep its contrast in dark mode.

Most of them. Of the 179 debugging designs: 118 are MIT, Apache 2.0, ISC, BSD, OFL or public domain, which allow commercial use with no credit. 56 are CC BY, which asks you to credit the author. 4 are share-alike or copyleft (CC BY-SA, GPL, MPL), so changes keep the license. 1 are for non-commercial use only. Each icon's page names its license, so check it before you ship.

56 of the 179 debugging designs are CC BY, which asks you to credit the author. 118 are MIT, Apache 2.0, ISC, BSD, OFL or public domain, which need no credit (most only ask you to keep the license notice if you ship their source files). Each icon's page names its license and author.

Yes. Every debugging icon is free to browse, copy and download here. Pro adds the MCP server, which installs icons for your AI agent.

1 debugging designs come from sets that are for non-commercial use only. Check the library on an icon's page before you pick it for a paid product.

With Pro, the shadcn.io MCP server lets Claude Code, Cursor or any MCP client search every library and install the debugging icon you describe.

Ask in plain words, like "a bug icon". search_icons matches an icon's name, keywords and tags, so the debugging tag helps it find them, and get_icon installs the one you pick. The tools are search_icons, get_icon and list_icon_libraries.