Explore extensions
Extensions can be used to extend the core k6 features to fit your performance-testing use cases. There are two main categories of extensions:
| Category | Maintainer | Audited | Cloud support |
|---|---|---|---|
| Official | Grafana Labs | ✅ Yes | ✅ Yes |
| Community | Community | ✅ Yes | ⚠️ Partial* |
* Partial cloud support means that the extensions can be used in the CLI with the --local-execution mode, and on Private Load Zones with a custom image. They don’t work on Grafana Cloud k6 Public Load Zones.
Official extensions
[en] DOCS_SHARED: "docs/k6/latest/extensions/explore.md" ("/hugo/content/docs/k6/latest/extensions/explore.md:21:1") shared page "docs/k6/latest/shared/official-extensions.html" not found
Community extensions
Note
We’re working on a process for community folks to submit their extensions.
[en] DOCS_SHARED: "docs/k6/latest/extensions/explore.md" ("/hugo/content/docs/k6/latest/extensions/explore.md:31:1") shared page "docs/k6/latest/shared/community-extensions.html" not found
Use extensions
There are two ways to use extensions when running a k6 test script.
Automatic extension resolution
These extensions can be used in your test without any additional configuration. They are automatically resolved and loaded by k6 when you import them in your test script.
Custom k6 binary
If you have developed your own k6 extension or want to use an extension that’s not available through automatic extension resolution, you have to build a custom k6 binary. The process involves using the xk6 tool to compile k6 with your desired extensions included. Custom binaries give you the flexibility to incorporate any extension from the k6 ecosystem.
Refer to build a custom k6 binary guide to learn how to create your own k6 binary with custom extensions.
Caution
Many other extensions maintained by members of the k6 ecosystem are available in GitHub. These extensions aren’t maintained nor audited by Grafana Labs.