Skip to content
Skills Library
Programming · Planning

bevy-rendering

/bevy-rendering

Use when choosing Bevy 0.19's built-in renderer versus an API-only, headless, or external renderer; selecting forward or deferred PBR; migrating `RenderGraph` nodes to render systems; configuring 2D/3D render Cargo features; or deciding how physics crates such as `bevy_rapier3d` relate to rendering.

Repository
bevy-skills ↗
Licence
MIT
Last repository change
25.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/audit_renderer_features.py, tests/test_audit_renderer_features.py

What it does and when to use it

Use when choosing Bevy 0.19's built-in renderer versus an API-only, headless, or external renderer; selecting forward or deferred PBR; migrating `RenderGraph` nodes to render systems; configuring 2D/3D render Cargo features; or deciding how physics crates such as `bevy_rapier3d` relate to rendering.

Original author description

Use when choosing Bevy 0.19's built-in renderer versus an API-only, headless, or external renderer; selecting forward or deferred PBR; migrating `RenderGraph` nodes to render systems; configuring 2D/3D render Cargo features; or deciding how physics crates such as `bevy_rapier3d` relate to rendering.

How it works

  1. First classify the need
  2. Built-in renderer
  3. Forward versus deferred
  4. Extend before replacing
  5. Headless or external rendering
  6. Rapier integration boundary
  7. Audit and references
Original SKILL.md headings · 150 lines, 624 words
SKILL.md preview
---
name: bevy-rendering
description: Use when choosing Bevy 0.19's built-in renderer versus an API-only, headless, or external renderer; selecting forward or deferred PBR; migrating `RenderGraph` nodes to render systems; configuring 2D/3D render Cargo features; or deciding how physics crates such as `bevy_rapier3d` relate to rendering.
license: MIT
compatibility: opencode,claude-code,cursor
metadata:
  tier: "2"
  area: render
  bevy_version: "0.19"
---

# Bevy 0.19 — rendering choices

Start with Bevy's built-in wgpu renderer unless a measured constraint requires a
custom path. Renderer replacement changes asset preparation, visibility, cameras,
materials, platform integration, and debugging—not just one plugin.

## First classify the need

| Need | Path |
|---|---|
| Ordinary 2D/3D game, editor, or visualization | Built-in `2d` / `3d` profile |
| Custom shaders or a special pass | Extend built-in rendering |
| Many dynamic lights on desktop-class GPUs | Consider deferred opaque rendering |
| Server simulation with no pixels | Headless `MinimalPlugins` profile |
| Existing proprietary/embedded renderer | `2d_api` / `3d_api` plus an explicit bridge |
| Physics, collision, character motion | [`bevy-physics`](../bevy-physics/SKILL.md); this does not select a renderer |

Do not replace the renderer because a physics crate is present.
`bevy_rapier3d` computes rigid-body simulation and queries. Its optional debug drawing
uses Bevy rendering, but Rapier is not a renderer.

## Built-in renderer

```toml
[dependencies]
bevy = { version = "0.19", default-features = false, features = ["3d", "ui"] }
```

```rust
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .run();
}

fn setup(
    mut commands: Commands,
    mut meshes: ResMut<Assets<Mesh>>,
    mut materials: ResMut<Assets<StandardMaterial>>,
) {
    commands.spawn((
        Mesh3d(meshes.add(Cuboid::new(1.0, 1.0, 1.0))),
        MeshMaterial3d(materials.add(Color::srgb(0.3, 0.7, 0.9))),
    ));
    commands.spawn((
        Camera3d::default(),
        Transform::from_xyz(0.0, 2.0, 4.0).looking_at(Vec3::ZERO, Vec3::Y),
    ));
    commands.spawn(DirectionalLight::default());
}
```

`3d` is a complete profile. `3d_bevy_render` is the lower-level collection that
selects Bevy's renderer; `3d_api` supplies world-side 3D types without a renderer.
Profiles only trim dependencies when `default-features = false`.

## Forward versus deferred

Forward is the default opaque method. Prefer it for broad platform coverage,
MSAA, lower bandwidth, fewer lights, and material flexibility. Deferred moves opaque
material data into a G-buffer and can reduce repeated geometry work with many lights,
but uses more bandwidth and does not support MSAA.

```rust
use bevy::{
    core_pipeline::prepass::{DeferredPrepass, DepthPrepass},
    pbr::DefaultOpaqueRendererMethod,
    prelude::*,
};

fn enable_deferred(app: &mut App) {
    app.insert_resource(DefaultOpaqueRendererMethod::deferred());
}

fn spawn_deferred_camera(mut commands: Commands) {
    commands.spawn((
        Camera3d::default(),
        Msaa::Off,
        DepthPrepass,
        DeferredPrepass,
    ));
}
```

This choice applies to opaque rendering. Transparent materials still need their
appropriate forward/transparent path. Benchmark representative content on minimum
spec hardware rather than selecting from light count alone.

## Extend before replacing

Use these escalation levels:

1. `StandardMaterial` properties and camera/post-process components.
2. `Material`, `Material2d`, or `MaterialExtension` for shader specialization.
3. A render-world extraction/prepare/queue pipeline.
4. A Bevy 0.19 render system in `Core2d` / `Core3d` for a custom pass.
5. A fully external renderer only when the earlier levels cannot meet the constraint.

Camera `ViewNode`/render-graph-node APIs were removed in 0.19. Render passes are
systems using `ViewQuery` and `RenderContext`, ordered against actual system functions
or `Core3dSystems`/`Core2dSystems` sets. The top-level schedule named
`bevy::render::renderer::RenderGraph` remains for non-camera work.

## Headless or external rendering

```toml
# Simulation/server: no render stack.
bevy = { version = "0.19", default-features = false, features = [
  "default_app", "multi_threaded", "serialize"
] }

# External renderer that consumes Bevy's world-side 3D types.
# bevy = { version = "0.19", default-features = false, features = [
#   "default_app", "3d_api"
# ] }
```

An external bridge must define ownership and synchronization for transforms, meshes,
materials, cameras, visibility, asset lifetime, GPU uploads, window/surface events,
and frame pacing. Keep renderer-specific handles in dedicated components; do not leak
them into gameplay components.

## Rapier integration boundary

For Bevy 0.19, `bevy_rapier3d 0.36` is the matching release line. Rapier defaults to
`PostUpdate` with a variable timestep; tick-coupled games may explicitly move it to
`FixedUpdate`. Drive a visible entity and collider from one authoritative transform
policy, and keep display-only smoothing separate. See
[`bevy-physics`](../bevy-physics/SKILL.md) and
[the physics boundary](references/physics-boundary.md).

## Audit and references

Run `python3 scripts/audit_renderer_features.py path/to/Cargo.toml` to catch common
profile and Rapier/debug-render mismatches.

- [Renderer decision guide](references/renderer-choice.md)
- [Bevy 0.19 render systems](references/render-systems.md)
- [Physics versus rendering](references/physics-boundary.md)
- [`bevy-cargo-features`](../bevy-cargo-features/SKILL.md)
- [`bevy-pbr-materials`](../bevy-pbr-materials/SKILL.md)
- [`bevy-physics`](../bevy-physics/SKILL.md)
- [`bevy-diagnostics-profiling`](../bevy-diagnostics-profiling/SKILL.md)
- [`bevy-vfx`](../bevy-vfx/SKILL.md)
- [`bevy-wasm-webgpu`](../bevy-wasm-webgpu/SKILL.md)
Files in this package (6)
  • SKILL.md 6 KB
  • references/physics-boundary.md 2 KB
  • references/render-systems.md 3 KB
  • references/renderer-choice.md 3 KB
  • scripts/audit_renderer_features.py 5 KB
  • tests/test_audit_renderer_features.py 3 KB

Versions

RepositoryScoreLicence
This page · chrisgliddon/bevy-skills100MIT
ianpurton/disposable-heroes100MIT

Database snapshot: 13.11.2026 · package version 5464f4c6ee3a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100bevy-pbr-materials
    Use when spawning `Mesh3d` with `StandardMaterial`, writing a Bevy 0.19 custom `Material` with `AsBindGroup`, enabling `shadow_maps_enabled` or contact shadows, configuring atmosphere entities, loading glTF `/std` material sub-assets, or selecting forward versus deferred PBR.
  • 100bevy-cargo-features
    Use when selecting Bevy 0.19 Cargo features such as `2d`/`3d`/`ui`/`audio`, composing `3d_bevy_render` or API-only `3d_api`, building headless with `default_app`, enabling `bevy_gilrs`, or debugging missing UI/audio/input after `default-features = false`.
  • 100bevy-cargo-features
    Use when picking Bevy 0.20 Cargo features — top-level `2d`/`3d`/`ui`/`audio`, mid-level `3d_api`/`3d_bevy_render`/`ui_api`/`common_api`, headless `default_app`, input opt-ins `mouse`/`keyboard`/`gamepad`, `bevy_curve` (was `bevy_math/curve`), `compressed_image_saver_universal`,…
  • 100bevy
    Use when starting any Bevy task, choosing between Update and FixedUpdate, picking Cargo feature flags, or recalling which sibling skill covers ECS, assets, rendering, UI, or migration. Routes to the right Bevy 0.20 skill and pins the engine version for downstream snippets.
  • 100bevy-project-foundations
    Pins a Bevy 0.20 crate, dev-profile opt-level, and plugin boundaries before gameplay systems exist. Use when starting a windowed or headless Bevy app. Keywords: Bevy, Cargo.toml, DefaultPlugins, MinimalPlugins, opt-level.
  • 100bevy-master
    Bevy ECS hub for Bevy 0.20+. Use when starting a Bevy game, choosing ECS boundaries, or picking a Bevy skill. Keywords: Bevy, ECS, bevy-master, schedules, plugins.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.