To debug a website in Safari, enable Safari’s developer features, open Web Inspector, and choose the panel that matches the symptom: Elements for page structure and styling, Console or Sources for JavaScript, Network for failed resources, and Timelines for performance activity. For layout issues, pair Web Inspector with Responsive Design Mode; for device-specific behavior, inspect the actual eligible device or app when possible.
Enable Safari’s developer features and open Web Inspector
- Open Safari settings and enable the features for web developers. The setting’s exact location or label can vary by Safari release; consult Safari Help if it differs. Once enabled, the Develop menu appears in the menu bar.
- Choose Develop > Show Web Inspector to open the inspector, or reopen the last-used inspector tab. Choose Develop > Show JavaScript Console to go directly to Console.
- Keep the page in the state that reproduces the problem. Inspecting the relevant page state makes it easier to connect what you see with the DOM, console output, or network activity.
Web Inspector is Safari’s built-in tool for inspecting and debugging HTML, CSS, and JavaScript. Apple documents its panels and workflow in Web Inspector documentation and menu options in the Develop menu guide.
Choose a panel based on the symptom
| Symptom | Where to start | What to check |
|---|---|---|
| Text or an element is missing, or styling looks wrong | Elements | Inspect the rendered DOM, select the affected node, and examine its styles. Temporarily changing a rule can test whether it is responsible; the edit is diagnostic and does not update your source files. |
| A click or interaction does nothing | Console, then Sources | Look for errors or warnings in Console. Use Sources to locate the relevant script and debug execution. Console also accepts JavaScript for interactive investigation. |
| An image, stylesheet, script, or API call fails | Network | Review the request’s status, response, and timing, then trace the failed resource back to the relevant code or service. |
| The page is slow, janky, or appears to use unexpected memory | Timelines | Record activity and correlate requests, JavaScript events, layout, rendering, CPU, and memory-related work. A recording is evidence for a hypothesis, not proof of a root cause by itself. |
Other panels
Apple also lists Storage, Graphics, Layers, and Audit among Web Inspector’s panels. Start with the panel tied to the problem, then use specialized views if the first evidence points there.
Debug JavaScript errors and interactions
- Reproduce the interaction that fails while Console is open.
- Read the resulting error or warning and identify the script and location it points to.
- Open Sources to find the relevant script and investigate its execution. Use Console’s interactive prompt to inspect values or try a small JavaScript expression.
- Change the application code, reload the page, and repeat the same interaction to check whether the observed behavior changed.
Console output can reveal where execution failed, but it does not automatically explain the underlying cause. Check the surrounding code and the state the page was in when the message appeared.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Investigate missing assets and failed requests
- Open Network and reproduce the page load or action that should fetch the resource.
- Find the relevant request and inspect its status, response, and timing.
- Use the request details to narrow the issue to the resource, application code, or service that produced the request.
- After making a correction, repeat the same request path and verify the expected response.
Network evidence helps distinguish a resource that was not requested from one that was requested but did not load as expected.
Test responsive layouts in Responsive Design Mode
- Choose Develop > Enter Responsive Design Mode. Apple documents Control-Command-R as a shortcut; verify it in your installed Safari version if it does not work with your keyboard or release.
- Try the widths and heights where the defect appears, rather than checking only a single preset size.
- Account for display pixel ratio when investigating behavior on a high-density screen.
- Keep Web Inspector available while resizing, select the affected element in Elements, and inspect the styles that apply at the failing size.
Responsive Design Mode previews viewport and display-pixel-ratio changes and can be used alongside Web Inspector. It is a diagnostic aid, not a replacement for checking a real target device when device-specific behavior matters. See Apple’s Responsive Design Mode documentation.
Rank #2
- By Aline Coquelle (Author)
- 300 Pages
- Over 350 Illustrations
- Silk Hardcover
- Imported
Inspect a connected iPhone, iPad, simulator, or app
For eligible targets, choose Develop > Inspect Apps and Devices and select the page or app content to inspect. Apple documents inspection for eligible Safari content, apps, simulators, and configured connected devices, including iPhone and iPad. The targets and options shown depend on the device, operating system, and app configuration.
Apple also documents configuring a device that has been paired over a cable for network connection when the Mac and device are on the same network. Service workers appear separately because they are shared across webpages. See Apple’s Inspect Apps and Devices guide and Develop menu documentation.
Rank #3
- Bright Starts Safari Buddies soft books for babies are learning toys that help baby identify animals, including monkey, lion, elephant, & more; colorful illustrations on every page
- Cause and effect toy with squeezable crinkle pages that baby will love; ribbon loops throughout book; sensory toys for babies provide additional texture and tactile stimulation for baby to enjoy
- Includes a C-link loop to easily attach as carrier toys, stroller toys & more so baby can learn and play on-the-go; newborn toys, baby toys and toddler toys
- Encourages development of baby’s auditory, visual and tactile senses while introducing them to jungle animals
- Easy to clean: simply wipe clean with damp cloth and mild soap; crinkle books for babies make great baby boy toys or baby girl toys at baby showers, birthdays, Christmas, Hanukkah & more
Record performance activity with Timelines
- Open Timelines and start a recording.
- Reproduce the slow or janky behavior while recording.
- Correlate requests, JavaScript events, layout, rendering, CPU, and memory-related activity around the time of the symptom.
- Form a hypothesis from the sequence of evidence, then change one suspected cause and record again to see what changed.
Do not infer a root cause from a visual symptom or one isolated event. A recording helps organize evidence, but interpretation still depends on the page behavior and code being investigated.
When to use WebDriver instead
Interactive Web Inspector is suited to investigating a behavior as it happens. Apple documents WebDriver as a separate route for automating Safari tests; it complements interactive debugging rather than replacing it. See Safari Developer Features.
Rank #4
- Used Book in Good Condition
Troubleshoot common setup and debugging problems
- Develop is missing: enable Safari’s web developer features in settings, then check the menu bar again. The settings path can differ by installed release.
- The shortcut does not open Responsive Design Mode: use Develop > Enter Responsive Design Mode directly and verify the shortcut documented for your local Safari version.
- The expected device or app is not listed: inspection is limited to eligible content and depends on the target’s device, OS, and app configuration. Confirm the target is configured for inspection; for a paired device using network connection, Apple specifies that it and the Mac be on the same network.
- A temporary style change disappears: inspector edits are diagnostic. Make the confirmed change in the site’s source files if it should persist.
- A performance recording does not identify the cause: correlate activity across the recording and test a specific hypothesis with another reproduction rather than treating one event as a definitive explanation.
Or skip the browser setup
If you need a screenshot rather than an interactive debugging session, ScreenshotNeo provides a website screenshot API and MCP server. A single GET request can return a PNG, JPEG, WebP, or PDF. For a quick capture, this cURL example saves a WebP screenshot of Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for the API details. ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; those steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents using Claude, Cursor, or another MCP client.
The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month with no card.
Frequently Asked Questions
Does Responsive Design Mode prove that a site works on a real iPhone?
No. It helps diagnose viewport and display-pixel-ratio behavior, but device-specific behavior should be checked on the actual target when it matters.
Can I inspect Safari content on an iPhone from a Mac?
Yes, for eligible content and configured devices. Use Develop > Inspect Apps and Devices; which targets appear depends on the device, OS, and app setup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
