Inspector Lab - DevTools

A movable in-page DevTools window for any browser, even iPad: DOM Inspector, Elements, Console, Network, Sources, Cookies, Storage.

Inspector Lab - DevTools puts a real DevTools window inside the page itself: a movable, resizable, dockable DOM Inspector with Elements, Console, Network, Sources, Cookies, and Storage panels. It works anywhere a browser can run extensions, including browsers that have no built-in DevTools at all, such as Orion on iPad and iPhone. WHY INSTALL IT Native DevTools live in a separate panel and simply do not exist on most mobile browsers. Inspector Lab injects the whole toolset into the page you are looking at, so you can debug on an iPad, inspect a site on a machine where you cannot open the browser's own tools, or keep a compact inspector floating over your app while you work. It stays on the page across reloads until you close it, and it never runs anywhere until you click it. WHAT IT DOES - Elements: a live DOM Inspector. Pick and highlight elements on the page, inspect the DOM tree, edit HTML attributes and text directly in the tree, author inline CSS the DevTools way (tap a property or value to edit in place, tap empty space to add a declaration, switch declarations off without deleting them — all validated), force element states (hover, active, focus, visited), and read computed styles with a box-model diagram. - Console: captures the page's console output (log, warn, error, and friends) with values colored by type and file:line source links, and evaluates JavaScript expressions you type, in the page's own context. - Network: records requests live as the page makes them, with method, status, type, timing, headers, and fetch/XHR request and response bodies in a DevTools-style details pane. - Sources: lists the page's scripts and stylesheets in a collapsible tree and loads any file's content on demand for reading, with syntax highlighting for HTML, CSS, and JavaScript. - Cookies: view, edit, add, and delete the cookies for the site you are inspecting. - Storage: view and edit localStorage and sessionStorage in place. - Window management: drag it, resize it, dock it to any edge of the viewport, or let it float. Light and dark themes, plus an optional classic Chrome DevTools look. INSTALLING ON IPAD AND IPHONE Orion by Kagi (free on the App Store) is the browser that makes this work on iOS and iPadOS: it installs Chrome Web Store extensions directly, so this listing is the install. Once: 1. Open the ••• menu and choose Settings. 2. Scroll to the Extensions group and turn on Chrome extensions. 3. Reopen the ••• menu, tap Extensions, tap the + button, and install Inspector Lab - DevTools from the Chrome Web Store. Orion's extension support on iOS and iPadOS is still in beta, and Apple limits which extension APIs any browser may offer there. The inspector is built for that gap: panels fall back to in-page sources when an extension API is missing, and say so on screen. Verified on a real iPad: Elements, Console, Sources, Cookies, and Storage all work; Network captures the page's fetch/XHR traffic live, while the headers of static resources (a desktop webRequest feature) stay out of reach. Orion on macOS installs this extension the same way, with the fuller desktop API surface. MOBILE AND TABLET, MORE BROADLY Chrome for Android does not support extensions at all, and Kiwi Browser, the long-standing workaround, was discontinued and archived in 2025. Its extension engine lives on in Microsoft Edge Canary for Android, which installs add-ons from the Edge Add-ons store, and a few smaller Chromium forks now ship similar support. Safari's own extension format is a different package that has to be distributed as an App Store app, not from here. That is the whole landscape today: on a tablet or phone, an extension-capable browser is the only way to get real in-page DevTools, and Orion is the shortest path to it. PRIVATE BY DESIGN The inspector activates only when you click the extension icon on a tab, using the activeTab permission, so it has no standing access to your browsing. Site access for the cookies panel and for staying attached across reloads is optional and requested per site, only when you ask for it. Everything you inspect stays in your browser: the extension has no server, sends no data anywhere, and collects nothing. There is no analytics, no telemetry, and no crash reporting, and because the whole thing is open source you can verify that rather than take it on trust. Full policy: https://github.com/luangjokaj/inspector-lab/blob/main/PRIVACY.md OPEN SOURCE MIT licensed. Source code, feature tour, and issue tracker: https://github.com/luangjokaj/inspector-lab