Published Sep 16, 2025 ⦁ Updated Nov 4, 2026 ⦁ 5 min read

Safari Developer Tools: How to Use Web Inspector to Debug Websites

Yes, Safari has developer tools: they're called Web Inspector, and they're built into Safari on the Mac but hidden by default. To open them, choose Safari > Settings > Advanced, check Show features for web developers, then press Option+Cmd+I on any page (Apple). The same Mac tools also debug Safari on iPhone, iPad and the iOS Simulator.

One thing surprises people coming from Chrome: release Safari still has no network throttling control as of November 2026. A built-in throttle exists only in Safari Technology Preview 253 and later; everywhere else you use Apple's Network Link Conditioner. Both are covered step by step below.

16.59%
Safari's worldwide browser share, October 2026 (#2 after Chrome)
44.74%
Safari's share of US mobile browsing, October 2026
6
throttling presets in Web Inspector (Technology Preview): 3G to Wi-Fi 802.11ac
Sep 23, 2026
network throttling returns in Safari Technology Preview 253

Because Safari's WebKit engine powers every iPhone browser and Safari holds almost half of US mobile traffic, the Safari web developer tools are not optional if you ship websites. People call them Safari DevTools, Safari browser developer tools, or simply the developer tools for Safari; they all mean Web Inspector. This guide covers the Safari developer tools as they work in Safari 27.2 (released October 2026) and Safari Technology Preview 255.

How to open developer tools in Safari (Mac)

  1. Open Safari and choose Safari > Settings (Cmd+,).
  2. Click the Advanced tab.
  3. Check Show features for web developers at the bottom. A Develop menu appears in the menu bar, and a new Developer tab appears in Settings.
  4. Open the page you want to debug and press Option+Cmd+I, or choose Develop > Show Web Inspector. You can also right-click any element and choose Inspect Element. Safari then opens Web Inspector with that element already selected (Apple).

Older guides tell you to check "Show Develop menu in menu bar". That was the old label for the same checkbox; the steps are otherwise the same. Once open, Web Inspector keeps inspecting that tab even as you navigate to other pages in it.

This is the whole answer to "how to inspect in Safari on a Mac": there is no separate download, no extension, and no F12 key. The Mac Safari developer tools ship with the browser and only need that one checkbox.

Safari developer tools shortcuts

These come from WebKit's keyboard shortcuts reference and Apple's Responsive Design Mode docs.

Action Shortcut
Show Web Inspector (open / close) Option+Cmd+I
Show JavaScript Console Option+Cmd+C
Enter Responsive Design Mode Control+Cmd+R
Show Page Source Option+Cmd+U
Start / stop element selection Shift+Cmd+C
Search all files and resources Shift+Cmd+F
Clear the console Cmd+K or Control+L
Web Inspector settings Cmd+, (while Web Inspector is focused)
Jump to tab 1-9 Option+Cmd+1 to 9
Pause / resume JavaScript Control+Cmd+Y or Cmd+\
Step over / into / out F6 / F7 / F8

The Develop menu and Developer settings

The Develop menu is more than a launcher for Web Inspector (Apple: Develop menu):

  • Open Page With: open the current page in another browser (including Safari Technology Preview) or in an iOS, iPadOS or visionOS Simulator if Xcode is installed.
  • User Agent: send a different user agent string, handy for debugging sites that sniff the browser instead of using feature detection. Our user agent checker shows what a browser actually sends.
  • Devices and Simulators: every connected iPhone, iPad, Vision Pro and running Simulator, each with its own submenu of inspectable pages.
  • Service Workers and Web Extension Background Content: inspect scripts that don't belong to one page.
  • Empty Caches: clear every cache Safari holds, useful when a server caches files you are editing.
  • Feature Flags: toggle upcoming web platform features (Stable, Preview, Testable, Developer) to test with or without them (Apple).

The Developer tab in Safari Settings holds switches for local development (Apple: Developer settings): allow remote automation (for WebDriver and AI agents), allow JavaScript from the Smart Search field or Apple Events, disable site-specific quirks, disable local file restrictions, disable cross-origin restrictions, and debug modes for Intelligent Tracking Prevention and Private Click Measurement.

The Web Inspector tabs

Web Inspector is split into tabs, with a navigation sidebar on the left, a details sidebar on the right and a console prompt at the bottom. Press Esc in any tab to open the split console. You can show or hide tabs by right-clicking the tab bar, and dock Web Inspector left, right, bottom or in its own window (WebKit: interface). WebKit documents each tab at webkit.org/web-inspector.

Tab What it's for Chrome DevTools equivalent
Elements Live DOM, CSS, box model, Grid/Flex overlays, fonts Elements
Console Logs, errors, JavaScript prompt Console
Sources Files, breakpoints, debugger, local overrides Sources
Network Every request, headers, timing, HAR Network
Timelines Performance recordings: layout, rendering, JS, CPU, memory Performance + Memory
Storage Cookies, Local/Session Storage, IndexedDB, Cache Storage Application
Graphics Canvas, WebGL/WebGPU, CSS and Web Animations Animations (partly)
Layers 3D view of compositing layers Layers
Audit Built-in and custom checks, such as accessibility Lighthouse (different scope)
Search Search every resource Search (Cmd+Option+F)
  • Elements: the live DOM and CSS. Edit styles, toggle classes, force :hover and other states (right-click a node > Forced Pseudo-Classes), inspect the box model, and see Flexbox and Grid overlays (Elements tab).
  • Console: the Safari developer console. Logs, errors, and a JavaScript prompt that runs in the page. $0 is the element selected in Elements (Console API).
  • Sources: the Safari debugger. Set breakpoints (line, event, DOM mutation, fetch/XHR, exception), step through code, and use source maps (Sources tab).
  • Network: every request with headers, timing, size, and response body. It has a Disable Caches checkbox that works while Web Inspector is open (Network tab). To replace a response with your own file, create a Local Override from the Sources tab. The full Network workflow is in its own section below.
  • Timelines: record page activity to profile network requests, layout and rendering, JavaScript and events, memory and CPU (Timelines tab, Apple).
  • Storage: cookies, Local and Session Storage, IndexedDB, and Cache Storage.
  • Graphics: canvas contexts, WebGL, and CSS/Web animations.
  • Layers: a 3D view of compositing layers and why each one was created (Layers tab).
  • Audit: run built-in or custom checks, such as accessibility audits, against the page (Audit tab).

Inspect element in Safari: Elements tab basics

Right-click anything and choose Inspect Element, or press Shift+Cmd+C and click on the page. In Safari, Inspect Element selects the node in the DOM tree and shows its rules in the Styles panel. From there:

  • Double-click a tag, attribute or text to edit it. Drag nodes to reorder them.
  • Click a value in Styles to edit it, or Add new rule to write a new selector. The Classes button toggles classes on and off.
  • The Layout panel lists every Grid and Flex container and toggles page overlays: track sizes, line numbers, line names, area names, and flex item order.
  • The Font panel shows the font actually used, with sliders for each axis of a variable font.
  • The Changes panel lists every CSS edit you made, so you can copy them back into your source file.
  • The Node panel shows attributes, accessibility data, and JavaScript event listeners, including those on ancestors.

Safari Web Inspector computed styles

The Computed panel answers "what value did this property actually end up with?" It draws the box model (margin, border, padding, content sizes) and lists computed values. By default, the Properties section shows only properties that differ from their initial value; open the filter and choose Show All to see everything, or Prefer Shorthands to collapse longhands. CSS custom properties get their own Variables section, which you can group by value type (WebKit: Elements tab). That page is the official Apple Safari Web Inspector computed styles documentation; Apple's own docs link to it.

The Safari developer console

The Safari console (the Console tab, Option+Cmd+C, also called the Safari browser console) shows everything the page logs, plus errors and warnings, and runs JavaScript in the page's context. Like most dev tools, Safari's console has a command line API (WebKit):

$0                     // the element selected in Elements
$$('a[target=_blank]') // querySelectorAll, as an array
copy(JSON.stringify(window.__STATE__)) // copy a value to the clipboard

Use the scope bar to filter by Errors, Warnings, Logs, Infos and Debugs, and the execution context selector to run code inside an iframe or extension. If you only need a developer console, Safari opens it straight from Develop > Show JavaScript Console.

Inspect cookies in the Safari Storage tab

The Storage tab lists cookies per domain with Name, Value, Domain, Path, Expires, Size, Secure, HttpOnly and SameSite columns (plus a Partition Key for partitioned cookies). Use Add Cookie, double-click to edit, or Delete and Clear Cookies to remove them (WebKit source), and the same tab holds Local Storage, Session Storage, IndexedDB and Cache Storage. For a single request, the Network tab's Cookies section shows exactly which cookies were sent and set (WebKit: Network tab). Safari's Intelligent Tracking Prevention can cap or block some third-party cookies, so a cookie that works in Chrome may be missing here; Settings > Developer > Enable Intelligent Tracking Prevention debug mode logs why.

Debugging JavaScript in Safari

Web Inspector is the debugging tool for Safari, and the Sources tab is its debugger. A typical Safari debugging session:

  1. Open Sources and find your file in the left sidebar (bundled code maps back to originals if your build emits source maps).
  2. Click a line number to add a breakpoint, or add debugger; to your code.
  3. Trigger the code. Execution pauses; inspect variables in the right sidebar and the call stack.
  4. Use the step buttons, or type expressions in the Console while paused. They run in the paused scope.

To stop on any thrown error, enable All Exceptions or Uncaught Exceptions in the Breakpoints section.

Other breakpoint types worth knowing, all added from the + button in the Breakpoints section or a right-click (Sources tab):

  • Event breakpoints: pause on any click, keydown or other event, or on timers and animation frames.
  • URL breakpoints: pause when a fetch or XHR request to a matching URL is sent.
  • DOM breakpoints: right-click a node in Elements > Break on subtree modifications, attribute changes or node removal.
  • Conditional breakpoints and actions: edit a breakpoint to add a condition, or make it log a message instead of pausing (a logpoint).
  • Blackbox Script: right-click a library file so stepping skips over it.

Safari network debugging: the Network tab

For Safari network debug work, open the Safari Network tab and reload the page. Web Inspector only records requests made while it is open (WebKit: Network tab).

Control What it does
URL filter and resource type buttons (Document, Image, Font, XHR/Fetch, Other and more) Narrow the list
Other filter options > Preserve Requests Keep requests across navigations (Safari's "preserve log")
Disable Caches Ignore cached resources while Web Inspector is open
Export (Cmd+S) / Import Save or load a HAR file
Right-click a request > Copy as cURL / Copy as fetch Replay the request in a terminal or the console
Right-click > Block Request URL Make a request fail, to test error handling
Right-click > Create Response Local Override Serve your own body, headers or status code
Throttling menu (Technology Preview only) Slow down requests, see the next section

Select a request to see Preview, Headers (with the redirect chain and the initiator's call stack), Cookies, Sizes, Timing and Security (TLS connection and certificate). Right-click the table header to add columns such as Status, Method, Protocol, Priority and IP Address. Safari 27 also shows every request in a redirect chain (WebKit: Safari 27.0).

To turn a copied cURL command into code for another language, paste it into our curl converter. Our HTTP status codes reference explains any odd status you see in the Status column.

Local overrides and blocked requests

Local overrides let you change what the network returns without touching the server (WebKit: Local Overrides):

  1. Select a request in the Network tab (or a resource in Sources).
  2. Click Create Local Override and choose Create Response Local Override, Create Request Local Override or Block Request URL.
  3. Edit the content, status, or headers. Check Regular Expression to match many URLs, or use Map to File to serve a file from disk on every match.
  4. Find and toggle overrides under Local Overrides in the Sources tab sidebar.

A response override with Skip Network checked never contacts the server, which is the quickest way to test your UI against an API that is down or not built yet.

Safari network throttling

This is where Safari differs from Chrome. Current release versions of Safari have no throttling control in Web Inspector: Safari 27.0, 27.1 and 27.2 (September to October 2026) don't list one (27.0, 27.1, 27.2). WebKit removed an earlier experimental version, and a new built-in throttling feature landed in Safari Technology Preview 253 (September 2026). Expect it in a future Safari release; until then you have two options:

  1. Safari Technology Preview: Apple's free preview browser, installed next to Safari, with the newest Web Inspector features.
  2. Network Link Conditioner: an Apple tool in the "Additional Tools for Xcode" download from developer.apple.com/download. Install the preference pane, pick a profile like "3G" or "Very Bad Network", and switch it on. It slows all traffic on the Mac, not just one tab, so turn it off when done.

On an iPhone, the same conditioner is built in once the device is enabled for development: Settings > Developer > Network Link Conditioner.

Which one should you use?

Method Where Scope Latency Bandwidth Packet loss Cost
Web Inspector throttling Safari Technology Preview on Mac The inspected page only Yes Yes No Free
Network Link Conditioner (Mac) macOS, any app Whole Mac Yes Yes Yes Free (Apple Developer account to download)
Network Link Conditioner (iOS) iPhone / iPad Developer settings Whole device Yes Yes Yes Free
Block Request URL override Any Safari Web Inspector Matching requests No No Fails the request Free
Best for testing one page's loading on a slow connection on a Mac: Safari Technology Preview throttling
Per page, no install beyond the preview browser, and it doesn't slow your other apps.
Best for testing real iOS Safari, PWAs and Home Screen web apps on a bad network: Network Link Conditioner on the iPhone
Remote Web Inspector on a device can't throttle yet, and this is built into iOS once Developer Mode is on.
Best for packet loss, DNS delay, or testing release Safari and the Simulator: Network Link Conditioner on the Mac
The only option with packet loss and custom profiles; remember it affects the whole Mac.

Why release Safari has no throttle: a short history

  1. July 2022WebKit adds experimental throttling to Web Inspector: an Allow throttling checkbox and bandwidth-only presets (3G, DSL, Edge, LTE) (commit).
  2. February 2024WebKit removes the experiment "pending correct SPIs" because it relied on a system API that couldn't throttle one process (commit). Guides from 2023 that mention the checkbox stop working.
  3. September 11, 2026A rebuilt throttler lands, with WebKit's own bandwidth and latency emulation, enabled on Apple platforms (PR #68710).
  4. September 17, 2026Safari 27.0 ships without it (release notes).
  5. September 23, 2026Safari Technology Preview 253: "Added support for network throttling of the inspected page" (release notes).
  6. October 22, 2026Technology Preview 255 fixes the Network tab's response timing so it accounts for throttling (release notes).
  7. October 2026Safari 27.1 and 27.2 release notes don't mention throttling, so release Safari still can't do it.

How to throttle network in Safari (Technology Preview)

Here is how to make Safari simulate slow network conditions from Web Inspector itself, the closest thing to Safari dev tools: throttle network the way Chrome does. It works only in Safari Technology Preview 253 or later, which needs macOS Sequoia or later (Apple).

  1. Download Safari Technology Preview from developer.apple.com/safari/technology-preview and install it. It runs alongside regular Safari and keeps its own settings.
  2. In Technology Preview, enable Show features for web developers (Settings > Advanced), the same as in Safari.
  3. Open the page and press Option+Cmd+I.
  4. Open Web Inspector's own settings: click the Settings tab (pinned at the end of the tab bar) or press Cmd+, while Web Inspector is focused.
  5. Go to Experimental and, under Network:, check Allow throttling.
  6. Open the Network tab. Next to Disable Caches there is now a throttling menu that reads No throttling. Pick a preset.
  7. Reload the page. The Network tab icon turns into a warning sign with the tooltip "Network throttling is enabled" so you don't forget it is on.
  8. Set the menu back to No throttling when you're done.

These steps come from the Web Inspector source: the "Allow throttling" setting lives in the Experimental settings group, and the menu is added to the Network tab's navigation bar only when that setting is on and the browser supports it (SettingsTabContentView.js, NetworkTableContentView.js).

Preset Bandwidth Added latency
No throttling unlimited 0 ms
3G 780 kbps 100 ms
DSL 2 Mbps 5 ms
Edge 240 kbps 400 ms
LTE 50 Mbps 50 ms
Wi-Fi 40 Mbps 5 ms
Wi-Fi 802.11ac 250 Mbps 2 ms
Safari Web Inspector throttling presets: bandwidth
Edge 0.24 Mbps
3G 0.78 Mbps
DSL 2 Mbps
Wi-Fi 40 Mbps
LTE 50 Mbps
Wi-Fi 802.11ac 250 Mbps

Values as defined in Web Inspector in Safari Technology Preview 255. Edge 0.24 and 3G 0.78 Mbps. Source: WebKit NetworkManager.js

How it works: latency delays the start of each request, and bandwidth buffers incoming data and releases it at the chosen rate (PR #68710). That means it throttles HTTP downloads for the inspected page, not your whole machine, and there is no custom profile, packet loss or "offline" preset yet.

For release Safari, the Simulator, or anything Technology Preview can't do (packet loss, DNS delay, custom speeds), use Apple's Network Link Conditioner (NSHipster):

  1. Sign in at developer.apple.com/download/all with a free Apple Account and search for Additional Tools for Xcode matching your Xcode or macOS version.
  2. Open the .dmg, then the Hardware folder, and double-click Network Link Conditioner.prefPane.
  3. It installs as a pane in System Settings. Open it and pick a profile: 100% Loss, 3G, DSL, EDGE, High Latency DNS, LTE, Very Bad Network, WiFi or WiFi 802.11ac.
  4. Flip the switch to ON and reload your page in Safari.
  5. For anything the presets don't cover, create your own profile with its own download and upload bandwidth, packet loss and delay.
  6. Turn it OFF when you're done. It slows every app on the Mac, including downloads, video calls and Xcode.

Throttle Safari on iPhone and iPad

iOS has the conditioner built in, so you can test real iOS Safari, Home Screen web apps and in-app browsers on a bad connection:

  1. Pair the device with a Mac once (plug it in with Xcode installed), then turn on Settings > Privacy & Security > Developer Mode and restart (Apple).
  2. A Developer section appears in Settings. Open it and, under Networking, tap Network Link Conditioner.
  3. Choose a profile (or add one), turn Enable on, and test in Safari. Inspect the page from your Mac as described below to watch the slowed requests in the Network tab.
  4. Turn it off afterwards: it affects every app on the device.

Troubleshooting slow-network tests

  • Times look too fast in Technology Preview. Update to release 255 or later; earlier builds didn't account for throttling in the reported response timing (STP 255).
  • Nothing is slower. Check Disable Caches in the Network tab; cached files load from memory or disk and skip the network entirely.
  • Only the first load is slow on iOS. A service worker may be serving the rest. Inspect it from Develop > [device] > Service Workers.
  • You need "offline". Release Safari can fake it per request with Block Request URL, or use the 100% Loss profile in Network Link Conditioner.

Safari mobile view: Responsive Design Mode

To use Safari Responsive Design Mode, choose Develop > Enter Responsive Design Mode (Control+Cmd+R). The page reloads in a resizable frame with presets for iPhone and iPad sizes, a device pixel ratio switch, and a user agent menu. It's good for checking layout and media queries quickly (Apple).

  • Viewport presets: pick a device size, or drag the handles on the sides and bottom corners. Your own size is saved as Custom size.
  • Rotate: swap width and height to check landscape.
  • Pixel Ratio: render at 1x, 2x or 3x to test srcset images and resolution media queries.
  • Zoom: shows when the viewport is bigger than your window and content is scaled down.
  • Open with Simulator: jump to a real iOS Simulator when you need the true mobile behavior.

It does not emulate the iOS browser itself: no real touch handling, no iOS-only keyboard and viewport behavior, and the engine is still desktop Safari. For those, use the Simulator or a real device, below. Apple warns that presets "don't represent exact layout, rendering, and behavior" on a device, for example the address bar and on-screen keyboard.

Safari developer tools on iPhone and iPad

iOS Safari has no inspector on the device itself. You inspect it from Safari on a Mac:

  1. On the iPhone or iPad, open Settings > Apps > Safari > Advanced and turn on Web Inspector (on iOS 17 and earlier, Settings > Safari > Advanced).
  2. On the Mac, enable Show features for web developers as above.
  3. Connect the device with a cable and tap Trust if asked.
  4. Open the page in Safari on the device.
  5. On the Mac, choose Develop > [your device name] > [the page]. Web Inspector opens against the live page on the phone (Apple).

For wireless debugging, connect by cable once, then choose Develop > [your device] > Connect via Network. The device then shows up in the Develop menu over Wi-Fi while both are on the same network. You can also inspect running service workers and foreground Home Screen web apps from the device's submenu, and the Develop > Inspect Apps and Devices window lists everything inspectable in one place, with options to auto-open Web Inspector for new service workers (Apple).

Web views in other apps are inspectable only if the app opts in. Since iOS 16.4, apps set isInspectable on their WKWebView (WebKit blog):

if #available(iOS 16.4, *) {
    webView.isInspectable = true
}

Chrome for iOS uses this too; see how to inspect Chrome on iPhone.

iOS Simulator

Install Xcode from the Mac App Store and launch it once so it finishes setup. Then, in Safari, choose Develop > Open Page With > [a Simulator] to open the current page in iOS Safari on the Simulator (Apple). Simulators always allow inspection, so the page appears under Develop > [Simulator name] on the Mac with no settings to change. It's the fastest way to test iOS Safari without hardware, though performance and some device features differ from a real phone.

To test older iOS versions, add a runtime in Xcode > Settings > Components and create a Simulator for it (Apple).

What's new in Safari 27 developer tools

Safari 27.0 shipped on September 17, 2026, for macOS 27, iOS 27, iPadOS 27 and visionOS 27, and as a separate install for macOS 26 Tahoe and macOS 15 Sequoia (WebKit). The Web Inspector changes:

  • Network: every request in a redirect chain is shown.
  • Elements: Subgrid and Grid-Lanes badges, and inline color contrast info in the Color Picker.
  • Timelines: the layout root element in Layout event details, a node column for layout and rendering events, and distinct colors for style events.
  • Console: you can redefine let and const variables at the prompt.

Safari 27 also includes a Model Context Protocol (MCP) server, so an AI coding agent can open tabs, read the DOM, take screenshots, read console messages and network requests, and click or type in Safari (Apple). Enable it in Safari > Settings > Developer > Allow remote automation and external agents, then register it with your agent:

claude mcp add safari-mcp -- "/usr/bin/safaridriver" --mcp

Technology Preview is ahead again: release 255 (October 22, 2026) adds a CSS keyframe animation editor, stack trace popovers, and evaluation previews in the console (STP 255).

Safari Web Inspector vs Chrome DevTools

Need Safari Web Inspector Chrome DevTools
DOM/CSS editing Elements tab Elements panel
JS debugging Sources tab Sources panel
Network throttling Technology Preview only (release Safari: use Network Link Conditioner) Built in
Throttling presets 3G, DSL, Edge, LTE, Wi-Fi, Wi-Fi 802.11ac (no custom yet) Fast 4G, Slow 4G, 3G, Offline, plus custom (Chrome)
Offline mode Block Request URL, or 100% Loss in Network Link Conditioner Offline preset
Request overrides Local Overrides (request, response, block) Overrides
Device emulation Responsive Design Mode Device Mode
Real iOS device debugging Yes, from a Mac No (iOS Chrome is WebKit)
Lighthouse-style audits Audit tab (custom checks) Lighthouse
AI agent access Built-in MCP server (Safari 27) Separate tools
Runs on Windows No Yes

Chrome DevTools, Safari's Web Inspector and Firefox's tools cover the same basics; the reason to use Safari's is that it's the only one that runs your page on WebKit, the engine behind every iPhone browser. For the Chrome side of things, see our Chrome debugging guide.

If you need iOS coverage across many devices, a cloud device service or an automated cross-browser suite helps; browse testing tools on DevHunt and QA tools. For native iOS work beyond the browser, see dev tools iOS developers use.

Troubleshooting Safari dev tools

Problem Fix
No Develop menu Safari > Settings > Advanced > Show features for web developers. On a managed Mac, an MDM profile can hide it.
Option+Cmd+I does nothing Enable the checkbox above first; click the page so it has focus.
iPhone not listed in Develop menu Turn on Web Inspector on the device, unlock it, tap Trust, try another cable, and update Safari on the Mac.
Page missing under the device The tab must be open in the foreground; for apps, the web view must set isInspectable.
Requests missing in Network tab Web Inspector records only while open: open it, then reload. Turn on Preserve Requests to keep them across navigations.
Changes don't appear after reload Check Disable Caches, or Develop > Empty Caches.
No throttling menu Release Safari doesn't have one; use Technology Preview or Network Link Conditioner (see above).

FAQ

Does Safari have developer tools?

Yes. Safari's developer tools are Web Inspector. They're hidden until you check Show features for web developers in Safari > Settings > Advanced. Developer tools: Safari includes the Elements, Console, Sources, Network, Timelines, Storage, Graphics, Layers and Audit tabs, which cover what Chrome DevTools does.

Why is "Show features for web developers" not showing?

It's at the bottom of the Advanced tab in Safari Settings. On older Safari versions the checkbox is called "Show Develop menu in menu bar". On a managed Mac, an MDM profile can hide developer features.

How do I open the console in Safari on iPhone?

There is no console on the phone itself. Enable Web Inspector in the iPhone's Safari Advanced settings, connect it to a Mac, and choose the page from Safari's Develop menu; the Console tab shows the phone's logs.

Can I use Safari developer tools on Windows?

No. There is no current Safari for Windows, and Web Inspector for iOS devices runs only on macOS. On Windows, use a cloud service with real Apple devices.

How do I throttle the network in Safari?

Release Safari doesn't have a built-in throttle yet, so network throttling in Safari means one of two tools. Use Safari Technology Preview, which added network throttling in release 253: open Web Inspector, go to its Settings > Experimental, check Allow throttling, then pick a preset such as 3G in the Network tab. Or use Apple's Network Link Conditioner, which slows the whole Mac's connection.

Can Safari throttle network speed for just one tab?

Only in Safari Technology Preview 253 and later, where Web Inspector's throttling applies to the inspected page. Network Link Conditioner, the only option for release Safari, slows every app on the Mac or iPhone.

What happened to the "Allow throttling" setting in Safari?

It was an experimental Web Inspector setting from 2022 until WebKit removed it in February 2024. It came back, rebuilt with latency support, in Safari Technology Preview 253 (September 2026) and is not yet in release Safari.

How do I open the Safari dev console?

Press Option+Cmd+C, or choose Develop > Show JavaScript Console. If the Develop menu is missing, enable Show features for web developers first. To keep a dev console, Safari also lets you press Esc in any other tab to show the console below it.

How do I make Safari open dev tools with a shortcut?

Option+Cmd+I opens Web Inspector on the last tab you used, Option+Cmd+C opens it on the Console, and Shift+Cmd+C starts element selection. There is no F12 shortcut in Safari.

How to inspect in Safari on Mac?

Right-click any part of the page and choose Inspect Element. If that menu item is missing, enable Show features for web developers in Safari > Settings > Advanced first.

Where is Safari's mobile view?

Choose Develop > Enter Responsive Design Mode (Control+Cmd+R) and pick an iPhone or iPad preset. For true iOS behavior, use Develop > Open Page With to open the page in an iOS Simulator.

Does Safari have a network tab and preserve log?

Yes. The Network tab lists every request while Web Inspector is open. To keep requests across page loads, open Other filter options in the filter bar and turn on Preserve Requests.