diff --git a/content/build/drivers/_index.md b/content/build/drivers/_index.md
index 16e0f0e319..40905f8732 100644
--- a/content/build/drivers/_index.md
+++ b/content/build/drivers/_index.md
@@ -32,6 +32,51 @@ The following table outlines some differences between drivers.
 | **Multi-arch images**        |             |         ✅         |      ✅      |         ✅         |
 | **BuildKit configuration**   |             |         ✅         |      ✅      | Managed externally |
 
+## Loading to local image store
+
+Unlike when using the default `docker` driver, images built using other drivers
+aren't automatically loaded into the local image store. If you don't specify an
+output, the build result is exported to the build cache only.
+
+To build an image using a non-default driver and load it to the image store,
+use the `--load` flag with the build command:
+
+```console
+$ docker buildx build --load -t <image> --builder=container .
+...
+ => exporting to oci image format                                                                                                      7.7s
+ => => exporting layers                                                                                                                4.9s
+ => => exporting manifest sha256:4e4ca161fa338be2c303445411900ebbc5fc086153a0b846ac12996960b479d3                                      0.0s
+ => => exporting config sha256:adf3eec768a14b6e183a1010cb96d91155a82fd722a1091440c88f3747f1f53f                                        0.0s
+ => => sending tarball                                                                                                                 2.8s
+ => importing to docker
+```
+
+With this option, the image is available in the image store after the build finishes:
+
+```console
+$ docker image ls
+REPOSITORY                       TAG               IMAGE ID       CREATED             SIZE
+<image>                          latest            adf3eec768a1   2 minutes ago       197MB
+```
+
+### Load by default
+
+{{< introduced buildx 0.14.0 >}}
+
+You can configure the custom build drivers to behave in a similar way to the
+default `docker` driver, and load images to the local image store by default.
+To do so, set the `default-load` driver option when creating the builder:
+
+```console
+$ docker buildx create --driver-opt default-load=true
+```
+
+Note that, just like with the `docker` driver, if you specify a different
+output format with `--output`, the result will not be loaded to the image store
+unless you also explicitly specify `--output type=docker` or use the `--load`
+flag.
+
 ## What's next
 
 Read about each driver:
diff --git a/content/build/drivers/docker-container.md b/content/build/drivers/docker-container.md
index 25fe7b0218..635a85ebea 100644
--- a/content/build/drivers/docker-container.md
+++ b/content/build/drivers/docker-container.md
@@ -71,31 +71,6 @@ WARNING: No output specified with docker-container driver. Build result will onl
 ...
 ```
 
-## Loading to local image store
-
-Unlike when using the default `docker` driver, images built with the
-`docker-container` driver must be explicitly loaded into the local image store.
-Use the `--load` flag:
-
-```console
-$ docker buildx build --load -t <image> --builder=container .
-...
- => exporting to oci image format                                                                                                      7.7s
- => => exporting layers                                                                                                                4.9s
- => => exporting manifest sha256:4e4ca161fa338be2c303445411900ebbc5fc086153a0b846ac12996960b479d3                                      0.0s
- => => exporting config sha256:adf3eec768a14b6e183a1010cb96d91155a82fd722a1091440c88f3747f1f53f                                        0.0s
- => => sending tarball                                                                                                                 2.8s
- => importing to docker
-```
-
-The image becomes available in the image store when the build finishes:
-
-```console
-$ docker image ls
-REPOSITORY                       TAG               IMAGE ID       CREATED             SIZE
-<image>                          latest            adf3eec768a1   2 minutes ago       197MB
-```
-
 ## Cache persistence
 
 The `docker-container` driver supports cache persistence, as it stores all the