Before you install: Solid DevTools only shows data for SolidJS apps that include the solid-devtools npm package. It does nothing on other sites.

Why it's a strong pick

Solid DevTools is built for one job: debugging SolidJS. It is open source under the MIT license, and its code is public on GitHub. It uses Manifest V3, Chrome's current extension format. The project's latest release, solid-devtools 0.34.5, came on 21 January 2026. The README labels the extension "In early development".

What it does

The README describes it as a Chrome Developer Tools extension for debugging SolidJS applications. Once your app loads the solid-devtools package, a Solid panel appears in DevTools. There you can look at Solid's reactivity graph and your component state and hierarchy.

Key features

Reactivity graph. Visualise and interact with how Solid's reactivity connects.
Component inspection. Look at component state and the component hierarchy.
Framework support. The README says it works with SolidStart and Astro.
DevTools panel. A Solid panel opens inside Chrome DevTools.
Open source. The code is public under the MIT license.

Who it's for

Solid DevTools is for developers who build with SolidJS and want to see why a value updates. It is not for general browsing. If your app does not use Solid, you will see nothing useful.

What permissions does Solid DevTools ask for?

We read the source build file, not the store listing. It lists no permissions. It does run a content script on all sites, and it adds a DevTools page and a toolbar popup. It needs Chrome 94 or newer. The store build may differ, so check the install prompt before you add it.

Do I need to change my app to use it?

Yes. The README says your app needs the solid-devtools npm package, called the debugger backend. After you add it, the Solid panel appears in DevTools. Without that package, the extension has nothing to read from your app, so add it before you test.

Can I trust its privacy?

We could not read the developer's privacy policy when we checked; read it before installing. The repository we read has no privacy statement. The source build asks for no permissions, but it does run a script on all sites, so install it only if you work with Solid.

Does it work with older versions of the package?

Not always. The README warns that the extension and the npm library change together and can break with older versions. Keep solid-devtools up to date in your app. If the panel stops working after an update, check the package version first.

FAQ

Is it only for SolidJS? Yes. It shows data for Solid apps only.

Is it open source? Yes, under the MIT license.

Is it actively updated? The latest release we found was 21 January 2026, so it is not the most frequently updated pick.

Good to know

Honest limit: the README calls the extension early in development, and its latest activity we found is January 2026. Use it as a debugging aid and keep the npm package and the extension in step.

Other developer tools to compare

Solid DevTools is one of 13 picks in our developer tools guide:

Redux DevTools: debug Redux state.
Apollo Client Devtools: inspect Apollo Client apps.
Preact Developer Tools: inspect Preact components.
Lighthouse: audit a page.
JSON Formatter: read JSON responses.
React Developer Tools: inspect React components.
Vue.js devtools: inspect Vue 3 apps.
Requestly: redirect URLs, modify headers and mock requests while you test.
Ember Inspector: inspect Ember.js apps.
MobX Developer Tools: debug MobX apps.
Refined GitHub: Simplifies GitHub and adds 100+ small improvements for repos and pull requests. Works on GitHub.com only. Open source.
Header Editor: Rewrites request and response headers, redirects and blocks requests with rules you set. The Chrome build is the Lite version. Open source.