Package selection guidance compiled from public package information, community data, and project usage.
The webcrypto package provides a cross-platform implementation of the Web Cryptography API for Flutter, enabling secure cryptographic operations such as key generation, encryption, decryption, and digital signatures across Android, iOS, Web, macOS, Windows, and Linux. It offers a consistent interface that mirrors browser-based Web Crypto APIs, making it easier to implement secure data handling in Flutter applications. The package is particularly useful for apps requiring strong security features without platform-specific code. It is maintained by Google and open-sourced on GitHub.
Use cases
Secure data encryption
Digital signature verification
Key management
Cross-platform cryptography
Secure token handling
Key features
Cross-platform compatibility
Matches Web Crypto API specification
Supports symmetric and asymmetric cryptography
Open-source and maintained by Google
No native code required
Suitable for
Apps needing secure data storage
Authentication systems
Secure communication protocols
Privacy-focused applications
Developers familiar with Web Crypto APIs
Considerations
Requires understanding of cryptographic concepts
Not suitable for high-performance crypto-heavy workloads
Depends on Dart's async model
Limited to standard Web Crypto algorithms
May require additional validation for production use
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Cross-Platform Web Cryptography Implementation
This package provides a cross-platform implementation of the
Web Cryptography API.
Disclaimer: This is not an officially supported Google product.
This packages provides an implementation of the
Web Cryptography API across multiple platforms. Outside the
browser, this package features a native implementation embedding
BoringSSL using dart:ffi. When used inside a
web browser this package wraps the window.crypto APIs and
providing the same Dart API as the native implementation.
This way, package:webcrypto provides the same crypto API on Android, iOS, Web, Windows, Linux and Mac.
BoringSSL, Chrome and Firefox implementations pass the same test cases.
Missing:
Exceptions and errors thrown for invalid input is not tested yet.
The native implementation executes on the main-thread, however, all expensive
APIs are asynchronous, so they can be offloaded in the future.
For a discussion of the API design of this package,
see doc/design-rationale-md.
System dependencies
When you have a dependency on package:webcrypto, it will use
hooks to build BoringSSL. Thus, your system
must have:
cmake, and,
a C compiler (like gcc or clang)
Limitations
This package has a few limitations compared to the
Web Cryptography API. For a discussion of parity with
Web Cryptography APIs see doc/webcrypto-parity.md.
deriveKey is not supported, however, keys can always be created from
derivedBits which is supported.
wrapKey is not supported, however, keys can be exported and encrypted.
unwrapKey is not supported, however, keys can be decrypted and imported.
AES-KW is not supported because it does not support encrypt/decrypt.
Compatibility notes
This package has many tests cases to asses compatibility across the native
implementation using BoringSSL and various browser implementations of the
Web Cryptography APIs.
At the moment compatibility testing is limited to native implementation,
Chrome, Firefox and Safari.
Known Issues:
Chrome and BoringSSL does not support valid ECDH spki-formatted keys exported
by Firefox prior to version 72.
Firefox does not support PKCS8 import/export for ECDSA and ECDH keys.
Firefox does not handle counter wrap around for AES-CTR.
Safari does not support P-521 for ECDSA and ECDH.
The browser implementation of streaming methods for encryption,
decryption, signing and verification buffers the entire input, because
window.crypto does not expose a streaming API. However, the native
implementation using BoringSSL does support streaming.
In browsers, operations backed by window.crypto.subtle require a secure
context. When loaded from an insecure context, package:webcrypto throws
UnsupportedError for those operations with guidance to use HTTPS or a
trustworthy local origin such as localhost. fillRandomBytes() continues
to work because it uses window.crypto.getRandomValues(), which browsers
expose outside secure contexts.