bevy_cef

A powerful Bevy plugin for embedding web content using the Chromium Embedded Framework (CEF). Render websites, local HTML files, and web applications directly onto 3D meshes or 2D sprites with full interactivity and bidirectional communication between JavaScript and Bevy.

https://github.com/user-attachments/assets/54f476d0-8eda-4030-a3f6-dc4f2f54209f

✨ Features

• 🌐 Full Web Browser Integration - Embed complete web pages with CSS, JavaScript, and modern web APIs
• 🎮 3D Mesh & 2D Sprite Rendering - Render web content on any 3D surface or 2D sprite
• ⚡ Interactive Input - Full mouse, keyboard, and touch input support with automatic event forwarding
• 🔄 Bidirectional Communication - Seamless data exchange between JavaScript and Bevy systems
• 📁 Local Asset Serving - Serve local HTML/CSS/JS files with hot reload support
• 🛠️ Developer Tools - Full Chrome DevTools integration for debugging
• 🎯 Navigation Controls - Browser history, zoom, audio controls, and more
• 🔒 Multi-Process Architecture - Secure CEF multi-process design for stability

Platform Requirements

Macos

On macOS, using CEF typically requires creating an app bundle. For development, this library provides a debug feature flag. Once enabled, you can run the app without needing the bundle.

[!NOTE] Use this feature only during development; for releases, bundle the renderer process and the CEF framework inside the app.

Installation debug tools

When using debug, you need to prepare a separate CEF framework and debug render process. Please follow the steps below to set it up.

> cargo install export-cef-dir
> export-cef-dir --force $HOME/.local/share
> cargo install bevy_cef_debug_render_process
> cp $HOME/.cargo/bin/bevy_cef_debug_render_process "$HOME/.local/share/Chromium Embedded Framework.framework/Libraries/bevy_cef_debug_render_process"

Bundling for Release

Install the bundling tools:

> cargo install bevy_cef_render_process
> cargo install bevy_cef_bundle_app

Bundle CEF into your .app:

> bevy_cef_bundle_app --app path/to/YourApp.app --bundle-id-base com.example.yourapp

Run bevy_cef_bundle_app --help for additional options.

Windows

On Windows, you need to place CEF libraries in the same directory as the application executable. Please run the following command to install the CEF framework to local. When you build the project, the libraries will be automatically copied to the executable's directory.

> cargo install export-cef-dir --force
> export-cef-dir --force "$HOME/.local/share/cef"

Render process binary (recommended)

Install the dedicated render process binary so that CEF launches it directly instead of re-using your main executable. This avoids the brief window flash that occurs when the main executable is re-launched as a subprocess.

> cargo install bevy_cef_render_process

The build.rs script automatically copies the installed binary next to your executable during the build.

Fallback

If you do not install the render process binary, CEF will re-launch your main executable for its subprocesses. To prevent those subprocess instances from briefly showing a window, call early_exit_if_subprocess() at the very beginning of main() — before any Bevy initialization:

fn main() {
    bevy_cef::prelude::early_exit_if_subprocess();
    // ... Bevy App setup ...
}

Examples

See examples/.

On macOS, you need to enable the debug feature:

cargo run --example simple --features debug

On Windows, no extra feature flag is needed:

cargo run --example simple

🌍 Platform Support

🤝 Contributing

We welcome contributions! Here's how you can help:

1. 🐛 Bug Reports - Open an issue with detailed reproduction steps
2. 💡 Feature Requests - Suggest new features or improvements
3. 🔧 Pull Requests - Submit bug fixes or new features
4. 📚 Documentation - Improve docs, examples, or tutorials
5. 🧪 Testing - Help test on different platforms

Development Setup

1. Clone the repository
2. Install Rust and Cargo
3. Install the debugging tool with reference to Installation debug tools.
4. Run cargo build --features debug to build the project

Version Compatibility

License

Licensed under either of

• Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.