WebView Inspector vs Tiny Web Inspector

WebView Inspector is a developer tool for iOS and macOS that lets you quickly load any URL in a native WebKit WKWebView and inspect it using Safari’s Develop menu. It supports camera and microphone permissions for testing media-rich web functionality like WebRTC. Just enable inspection via WKWebViewConfiguration (isInspectable = true), connect your device or simulator to Safari, and debug your app as if it were running directly in the browser. Key Features: • Load any URL in a WKWebView on iOS and macOS • Inspect using Safari → Develop → [Your App] • Enable camera & microphone access for media testing • Native navigation: back, forward, refresh • Secure HTTPS with ATS support • Cross-platform testing in a single app Perfect for web developers, QA engineers, and testers who want a lightweight WebView testing tool without building a full environment.

Inspect and debug websites directly on your iPhone and iPad with Tiny Web Inspector. Browse a page and keep your developer tools close at hand. NETWORK Follow page resources, Fetch and XMLHttpRequest activity. Filter requests by resource type, status or host, search captured data, inspect available headers and bodies, and copy requests as cURL. ELEMENTS Browse and search the HTML tree. Use Touch selection to find a visible element, inspect its HTML, and copy its path or source. CONSOLE Read console.log, warnings and errors. Run JavaScript with quick commands and command history to investigate the current page. STORAGE Inspect local storage, session storage and cookies. Search, copy, edit or remove values, and view JSON in a readable format. WEB ENVIRONMENT Try User Agent presets, manage custom headers and inject your own scripts. Keep multiple pages open in separate tabs. ADAPTIVE WORKSPACE Use the inspector on iPhone and iPad, with layouts adapted for iPhone Duo's outer and inner displays. On the expanded Duo layout, browse alongside the inspector. Capture availability depends on WebKit and the resource type. Some browser-managed headers, cross-origin resources, binary payloads and navigation response bodies may not be exposed. Large captured bodies and older logs are limited to keep memory usage bounded.