float32-renderable
Specification: WebGPU § plain-color-formats
While WebGPU compatibility mode was being designed, rendering to 32-bit float color formats was briefly optional there, because OpenGL ES 3.1 only provides it through an extension. The draft specification gained float32-renderable in December 2024 to mark adapters that could use r32float, rg32float, and rgba32float as render attachments; core adapters were required to support it.
In February 2025 the working group made the capability a requirement of compatibility mode instead and dropped the token. WebKit had already implemented it, so Safari and other WebKit-based browsers still list it among adapter features, while browsers following the current specification do not. The percentage here therefore tracks the WebKit share of reports, not a hardware capability - the by-browser split below shows it directly.
Do not request float32-renderable or use it as a support test: a browser that does not know the name throws from requestDevice(). Every WebGPU device can use the 32-bit float formats as render attachments without enabling anything. What remains optional is blending into them, float32-blendable, and linear filtering when sampling them, float32-filterable. The sibling token for 16-bit formats is float16-renderable.
Availability by month
| Month | With feature | Eligible reports | Availability |
|---|---|---|---|
| 2026-08 | 55 | 238 | 23.1% |
| 2026-09 | 22 | 175 | 12.6% |
| 2026-10 | 39 | 371 | 10.5% |
| 2026-11 | 23 | 172 | 13.4% |
By browser (last 30 days)
| Browser | Availability | n |
|---|---|---|
| chrome | 0.0% | 250 |
| edge | 2.1% | 47 |
| firefox | 0.0% | 50 |
| safari | 100.0% | 37 |
| opera | 0.0% | 4 |
| samsung | 0.0% | 4 |
Availability = share of first-party, non-quarantined reports with WebGPU on a hardware (non-fallback) adapter that expose this feature. Developer-leaning sample. Full methodology.