English | 简体中文
Real Chrome DevTools inside any web page, phones included.
Screenshots: WebMC, a Minecraft in WebGL, with devtools-anywhere. Left: device mode on a computer. Right: on a phone.
| devtools-anywhere | eruda / vConsole | Chii | |
|---|---|---|---|
| UI | The latest Chrome DevTools | A panel of their own | An old Chrome DevTools (about 122) |
| The page's earliest logs and errors | Captured from the first script | Lost until they load | Captured |
| Setup | One <script> or a Vite plugin |
One <script> |
Cumbersome |
Vite, during vite serve only:
npm i -D @devtools-anywhere/vite-plugin// vite.config.js
import devtoolsAnywhere from '@devtools-anywhere/vite-plugin'
export default { plugins: [devtoolsAnywhere()] }Any page, from a CDN, first in <head>:
<script src="https://cdn.jsdelivr.net/npm/devtools-anywhere@0.2.0/dist/probe.iife.js"></script>Open the page and tap the F12 button.
A page on a phone, from a computer:
npx -p @devtools-anywhere/remote-server devtools-anywhere-remoteAdd the printed <script> to the page, open the printed target list on the computer, and click "inspect".
Self-hosting, every option and the element: see the usage guide.
<script> attribute |
Vite option | Effect |
|---|---|---|
data-open-immediately |
openImmediately |
Opens DevTools as the page loads |
data-default-shell-mode="off" |
defaultShellMode: 'off' |
No shell mode: the panel covers the page |
data-no-toggler |
noToggler |
Hides the F12 button |
data-remote |
remote |
Connects to a remote debugging server |
Shell mode (on by default) puts the page in an iframe, so DevTools stay open across reloads and device mode works: see shell mode.
| Panel | Support |
|---|---|
| Elements, Styles | Supported: without the browser's default styles |
| Console | Supported: including the page's earliest output |
| Network | Supported: no real timing; no WebSocket handshake headers |
| Sources | Partly supported: files and snippets, no breakpoints |
| Application | Supported |
| Device mode | Partly supported: shell mode only; size only, not pixel ratio, user agent or touch |
| Screencast, screenshots | Partly supported: redrawn from the DOM, not the screen's pixels |
| Performance, Memory, Profiler | Not supported: page scripts cannot get this data |
The page side uses only standard web APIs and works in any modern browser; the DevTools UI is verified in Chrome only. All the limits: see limitations.
| Package | For |
|---|---|
devtools-anywhere |
The probe and the in-page element |
@devtools-anywhere/devtools-frontend |
The DevTools frontend (English and Chinese UI) |
@devtools-anywhere/devtools-frontend-locales |
Optional: the other 80 UI languages |
@devtools-anywhere/vite-plugin |
Vite plugin |
@devtools-anywhere/remote-server |
Remote debugging server and CLI |
- Usage guide: every way to set it up, the options
- Limitations: what cannot be done, and where it differs from Chrome
- Design: how it works and why
- Development guide: setup, tests, releases
MIT. Third-party code in the published packages (the Chrome DevTools frontend, snapDOM, es-module-lexer) and its licenses: THIRD_PARTY_LICENSES.md.

