docs.rs Switches to Single Default Build Target on May 1 to Cut Costs

Every crate published to crates.io without a `[package.metadata.docs.rs]` targets list has, until now, received documentation built across five separate targets automatically. Starting May 1, that changes: docs.rs will build against a single default target, `x86_64-unknown-linux-gnu`, and nothing else unless you ask for more.

The Rust infrastructure team announced the shift on April 4, framing it plainly as a breaking change for crates that relied on the old multi-target default without ever declaring it. The reasoning is straightforward: the Rust ecosystem has grown to the point where building five target variants per crate, across thousands of published packages, burns substantial CPU, memory, and queue time. The team's assessment is that the vast majority of those builds are redundant, because most crates produce identical documentation regardless of target.

That calculus shifts for crates with platform-specific APIs. If your crate exposes anything behind a `#[cfg(target_arch = "wasm32")]` gate, or surfaces Windows- or macOS-specific interfaces, your documentation is genuinely different across targets and users actually need those platform-specific pages. For those crates, the fix is explicit: add a `[package.metadata.docs.rs]` section to your `Cargo.toml` and list the targets you need. Common examples include `wasm32-unknown-unknown` for WebAssembly crates and `x86_64-pc-windows-msvc` for anything touching the Windows API. You can also set `default-target` there to control which target renders at the top-level docs URL.

The transition window is short but deliberate. Maintainers have from April 4 to May 1 to audit their crates and add explicit target declarations where they matter. Community posts and translations surfaced within hours of the announcement, and several already walk through the exact Cargo.toml syntax needed to preserve multi-target builds.

For most crate authors, no action is required. If your library is a pure-Rust utility with no platform-conditional surface area, your docs were already identical across all five targets; the change loses you nothing. The performance win for the infrastructure, however, is cumulative across the entire ecosystem.

The infrastructure team also pointed to complementary work underway: donated CDN and shielding optimizations are being layered in to further reduce load on the build service. The single-target default is part of a broader push to keep docs.rs responsive as the crate count continues to climb, not a one-off cost cut.