variable](/manuals/build/building/variables.md#buildx_builder) to select the cloud builder.
## Loading build results
Building with `--tag` loads the build result to the local image store
automatically when the build finishes. To build without a tag and load the
result, you must pass the `--load` flag.
Loading the build result for multi-platform images is not supported. Use the
`docker buildx build --push` flag when building multi-platform images to push
the output to a registry.
```console
$ docker buildx build --builder cloud-<ORG>-<BUILDER_NAME> \
--platform linux/amd64,linux/arm64 \
--tag <IMAGE> \
--push .
```
If you want to build with a tag, but you don't want to load the results to your
local image store, you can export the build results to the build cache only:
```console
$ docker buildx build --builder cloud-<ORG>-<BUILDER_NAME> \
--platform linux/amd64,linux/arm64 \
--tag <IMAGE> \
--output type=cacheonly .
```
## Multi-platform builds
To run multi-platform builds, you must specify all of the platforms that you
want to build for using the `--platform` flag.
```console
$ docker buildx build --builder cloud-<ORG>-<BUILDER_NAME> \
--platform linux/amd64,linux/arm64 \
--tag <IMAGE> \
--push .
```
If you don't specify the platform, the cloud builder automatically builds for the
architecture matching your local environment.
To learn more about building for multiple platforms, refer to [Multi-platform
builds](/build/building/multi-platform/).
## Cloud builds in Docker Desktop
The Docker Desktop [Builds view](/desktop/use-desktop/builds/) works with
Docker Build Cloud out of the box. This view can show information about not only your
own builds, but also builds initiated by your team members using the same
builder.
Teams using a shared builder get access to information such as:
- Ongoing and completed builds
- Build configuration, statistics, dependencies, and results
- Build source (Dockerfile)
- Build logs and errors
This lets you and your team work collaboratively on troubleshooting and
improving build speeds, without having to send build logs and benchmarks back
and forth between each other.