Capabilities

Capabilities are the device and platform APIs that let a PWA do what native apps do — read and write local files, share content, reach hardware, accelerate graphics, and take payments. Most are gated behind a secure context, a user gesture, and an explicit permission, and support varies by engine.

Each entry explains what an API does, its permission and security model, where it is supported, and the fallback when it is not.

In this section

File System Access APIshowOpenFilePicker / showSaveFilePicker / showDirectoryPicker, file handles, permissions, and the Safari/Firefox fallback.

Web Share APIInvoke the native OS share sheet with navigator.share() to share URLs, text, and files.

Payment Request APIBrowser-mediated checkout: native payment sheet, digital wallets, and the canMakePayment() check.

Geolocation APIAccess the user's position with explicit permission. getCurrentPosition, watchPosition, and the permission model.

Async Clipboard APIRead and write the system clipboard. Permission model, rich content, and the execCommand fallback.

Web Bluetooth APIConnect to BLE devices via a browser device picker. WICG spec, Chromium-only, GATT service model.

Screen Wake Lock APIPrevent the screen from dimming. Automatic release on page hide and the re-acquire pattern.

WebCodecsLow-level, hardware-accelerated encoding and decoding with VideoEncoder, VideoDecoder, AudioEncoder, and AudioDecoder.

WebRTCRTCPeerConnection, MediaStreamTrack, and RTCDataChannel for peer-to-peer audio, video, and data — plus getUserMedia and signaling.

Planned topics

Reserved in the coverage matrix and filled in over time:

• Protocol handlers

← Back to the Reference overview.