Capability Matrix
What Can Your Browser Do?
56 browser capabilities across AI, storage, compute, and connectivity — tested live the moment this page loads.
Understanding Every Signal
What each capability check confirms about your browser's actual real-time support.
Scores & Storage
Capability Score & Capabilities Detected
The score is calculated from the 56 capabilities tested, weighted by how relevant each is to modern web application functionality. The detected count is how many of those 56 returned a positive result in your current browser — a browser with 50/56 is significantly more capable than one with 30/56 for advanced web applications.
Storage Quota & Storage Usage
Storage quota is the maximum space the browser will allow this origin to use across all storage mechanisms combined — IndexedDB, Cache API, and localStorage. Usage is how much of that quota is currently consumed. In private browsing, quota is typically reduced to a small fraction of the normal allocation.
Device APIs
Battery Charging & Battery Level
Reported by the Battery Status API where available. This API was removed from Firefox over fingerprinting concerns — the combination of battery level and charging state over time is a surprisingly effective cross-site tracking signal. Chrome still exposes it on Android; iOS Safari reports it partially. A "—" here means the API is unavailable in this browser.
Notification Permission
The current notification permission state for this origin. Shown here because notification permission is one of the permissions most commonly requested without a clear user benefit, and knowing whether it was previously granted (or denied) to IntelReap is useful context.
What the Grid Shows
The 56 capabilities across AI, compute, connectivity, storage, and graphics
The grid above each maps a single modern browser API to a green (supported) or red (not supported) tile. The categories cover: AI inference (WebNN, ONNX), graphics acceleration (WebGL2, WebGPU, OffscreenCanvas), compute (WebAssembly SIMD, SharedArrayBuffer, Web Workers), connectivity (WebSockets, WebRTC, Bluetooth, USB, Serial, NFC), storage (IndexedDB, Cache API, OPFS, File System Access), sensors (Geolocation, DeviceMotion, Ambient Light), and a miscellaneous tier including Speech Recognition, Web Share, Badging, and others. The exact combination of what's supported is browser- and platform-specific — Safari, Firefox, and Chrome differ significantly on Bluetooth, NFC, and several AI-related APIs.
Why Browser Capabilities Vary So Much
Different browsers implement different parts of the web platform
There is no single browser that supports every modern web API. Chrome leads on hardware APIs (Bluetooth, USB, NFC, Serial) through its Project Fugu initiative. Safari leads on some iOS-specific integration. Firefox prioritises privacy and standards compliance, which means some APIs available in Chrome are deliberately not implemented. The capability matrix makes these differences concrete rather than abstract.
Missing capabilities explain application failures
When a web application doesn't work in your browser, the capability matrix is often the fastest way to understand why — a missing API tiles up immediately as a red cell in the relevant category, correlating directly with the broken feature.