Debrowser
Coming to the App StoreComing soon

For iPhone, iPhone Duo and iPad

Inspect the page you're on.

Debrowser is a browser with desktop-class developer tools built in. Elements, Styles, Console, Network, Sources and Storage run on the device itself. No Mac, no cable, no proxy.

Coming to the App StoreComing soonRead the docs

In development. Requires iOS and iPadOS 27 or later.

Illustration of the inspector. Screenshots follow with the first release.

No Mac. No cable.

The bug is on the device. So is the inspector.

Debrowser is one app. Browser and inspector share the same process, so there is nothing to pair, trust or proxy. Open a page, inspect it, close the lid.

  1. 01

    Open the page

    A real browser with tabs, private tabs, profiles, bookmarks and history. Open the site you're working on, or a local project folder.

  2. 02

    Tap Inspect

    The inspector opens next to the page on iPad, as a drawer over it on iPhone. The page stays live, and on iPhone it keeps its viewport.

  3. 03

    Pick the element

    Tap or point at anything. The DOM tree jumps to it, Styles shows the matching rules, and edits apply to the page in front of you.

Instrumentation never rewrites a page's behaviour: native descriptors and return values are preserved, and a pristine mode loads the page with nothing injected at all.

iPad

Desktop-class, because the iPad is one.

Text tabs, a Styles side pane, a Network waterfall and a console drawer, laid out the way desktop tools are. Familiar to Chrome DevTools users, built with public Apple APIs.

Dock right, bottom or left, resize by dragging, or move the inspector into its own window.

  • Elements

    Live DOM tree, picker, search, attribute and HTML edits, highlight on the page.

  • Styles

    Matched and inherited rules, computed values, box geometry, declaration edits and toggles.

  • Console

    Logs and errors with levels and filters, inline objects, multiline JavaScript evaluation.

  • Network

    Request table and waterfall, headers, payload, preview, timing, cookies, HAR export.

  • Sources

    Raw, live DOM and pretty views with highlighting, search and source-map actions.

  • Storage

    Cookies, local and session storage, read-only IndexedDB, cache previews, quota.

  • Responsive

    Presets, custom sizes, rotation, Fit or 1:1, rulers, real viewport readback.

  • Info

    Page metadata, headers and security details, PNG, PDF and web-archive export.

  • Accessibility

    Roles, names, focus order, headings and landmarks, derived from DOM and CSS.

  • Resources

    Everything the page loaded, with previews for images, fonts and media.

Keyboard and trackpad

Hover states, right-click menus and shortcuts that match desktop habits. Every shortcut is also in the command palette.

Toggle the inspector
⌘⌥I
Pick an element
⌘⇧C
Device toolbar
⌘⇧M
Console drawer
Esc
Command palette
⌘K

iPhone and iPhone Duo

One layout model. It reads the width, and the fold.

There is no phone version and tablet version. The inspector adapts to the width class it gets, so an iPhone, a folded Duo and a narrow Split View half all get the same drawer, and an open Duo gets the iPad layout.

iPhone

In the current build

The inspector is a drawer over the page, never a panel squeezed beside it. The page keeps its viewport while the drawer moves, so layouts and media queries stay exactly as they were. Pick with a tap; the drawer stays where you left it.

iPhone Duo

Fold layout in development

Closed, the outer display gets the iPhone drawer. Open flat, the inner display gets everything the iPad has. Half folded, the divider snaps to the hinge: page on one side, inspector on the other. The fold-aware split is being built against Apple's iPhone Duo APIs and will be verified on hardware.

Honest data

Every value says where it came from.

Apps don't get everything a desktop browser's own inspector gets. Debrowser doesn't paper over that with zeros. Each value carries its source and confidence; a missing one shows a dash and the reason.

exact
Read directly from WebKit or the request pipeline.
approximate
Shown with ≈. A good estimate, never passed off as a measurement.
inferred
Shown in italics. Derived from other data, such as a stack matched from timing entries.
unavailable
Shown as — with the reason. WebKit does not expose it, or it was not captured.

The same rule applies everywhere: CSS pseudo-state overrides are labelled simulations, a re-fetched source is labelled replay, the accessibility view says it is derived from DOM and CSS rather than the engine's tree. What WebKit exposes, and what it doesn't.

Privacy

Nothing to collect, so nothing is collected.

The sites you visit make their ordinary requests to their own servers. Everything the inspector sees stays with you. Planned App Store privacy label: Data Not Collected.

  • Local

    Inspection, history, captures and exports stay on the device. You choose what to share.

  • No account

    Nothing to sign up for, nothing to sign in to. Buy it once from the App Store and open it.

  • No analytics

    No analytics SDK, no crash reporter, no developer-operated collection of any kind.

  • Public APIs only

    Built on WebKit with public Apple APIs. All inspector code ships inside the app; none is downloaded.

Read the privacy policy

Pricing

Pay once. Keep it.

A developer tool should cost what a developer tool costs: one price, paid once, owned.

One-time purchasePrice announced at launch
  • Every panel on iPhone, iPhone Duo and iPad
  • One purchase for all your devices
  • No subscription, no account
  • Updates through the App Store
Coming to the App StoreComing soon

Debrowser needs iOS and iPadOS 27 or later. Refunds go through Apple.

Questions

Good questions.

The longer answers live in the docs.

Does it need a Mac?

No. Debrowser runs the browser and the inspector in one app on the iPhone, iPhone Duo or iPad. There is no cable, desktop companion, proxy or pairing step.

Which pages work?

Any page the app's web view can open. Pages that block injected scripts or run in locked-down frames expose less; the inspector shows what it could read and says what it couldn't.

Why do some values show a dash?

WebKit does not expose everything to apps: outgoing cookie headers, remote addresses and some timing phases, among others. Where a value is unavailable you see a dash and the reason, not a zero.

Is there a debugger?

No. Apps on iOS cannot attach a JavaScript debugger or profiler to their own web view, so there are no breakpoints or step-through debugging. Console evaluation, logging and source views are there.

Does it change how the page behaves?

The runtime preserves native descriptors and return values, and on iPhone the inspector overlays the page instead of resizing it. A pristine mode reloads the page with nothing injected.

What about privacy?

Everything stays on the device. There is no account and no analytics. The app is built with public Apple APIs only, and every line of inspector code ships inside it.

How do refunds work?

Purchases and refunds go through Apple. Request one from your Apple account's purchase history.