What Is wgpu?
wgpu is a native, open-source Rust GPU library that runs directly on Vulkan, Metal, and DirectX 12 — no browser required. It implements the WebGPU graphics standard as its wire format, but runs as a native application talking straight to your graphics driver, not inside a browser's JavaScript sandbox. Unlike standard canvas or SVG rendering — which use the CPU — wgpu offloads rendering work to the GPU, enabling real-time post-processing effects like bloom, glow, and motion blur at high frame rates and resolutions.
wgpu is the engine that lets framechart, a native DaVinci Resolve plugin, produce cinematic-quality animated chart output — including 4K resolution and visual effects — rendered directly inside your Resolve timeline.
How wgpu Differs from Standard Canvas/SVG
| Property | wgpu | Canvas / SVG |
|---|---|---|
| Rendering hardware | GPU (hardware-accelerated) | CPU (software rendering) |
| Post-processing effects | Bloom, glow, motion blur, AA | Not available |
| Max resolution | 4K+ (limited by GPU) | Limited by CPU performance |
| Frame rate at 1080p | 60fps smooth | May drop frames with effects |
| Data privacy | Fully on-device | Fully on-device |
| Runtime | Native — inside DaVinci Resolve | Browser or native |
wgpu in framechart
framechart uses wgpu as its rendering engine for all chart animations, running natively inside the DaVinci Resolve plugin. This enables several capabilities that standard 2D chart libraries cannot produce:
Cinematic templates use post-processing bloom — bright chart elements glow and bleed light onto the surrounding area, creating depth and cinematic quality.
Fast-moving bars and lines produce motion blur during animation, making the motion feel physically real rather than mechanical.
framechart renders at your Resolve timeline resolution — including 4K (3840×2160) and beyond — using native GPU acceleration.
Frames are read from the GPU buffer and delivered straight into your Resolve timeline. No server processes the video data.
Platform Support
Because wgpu is native rather than browser-based, support is a question of operating system and GPU, not browser version.
Vulkan or DirectX 12. CUDA frame delivery on NVIDIA, OpenCL on AMD/Intel.
Metal, on both Apple Silicon and Intel Macs.
Vulkan. Interop path in progress — see the roadmap.
wgpu and Data Privacy
Because wgpu renders graphics on your local GPU, framechart's entire rendering pipeline is on-device. Your CSV data is read, laid out, rendered to a GPU framebuffer, and delivered into your Resolve timeline — all without leaving your computer.
This contrasts with server-side rendering tools, which upload your data to a remote server for processing. For journalists, financial analysts, and agencies handling confidential client data, on-device rendering is a meaningful privacy advantage.
wgpu vs. Server-Side Rendering
Many chart animation tools process video on cloud servers — your data is uploaded, rendered remotely, and the video is returned for download. framechart's wgpu approach renders everything locally, on your own machine.
- —Data leaves your device
- —Dependent on server availability
- —Rendering speed limited by server queue
- —Bandwidth required for upload and download
- —Data stays on your device
- —Works fully offline
- —Rendering speed scales with your GPU
- —No upload bandwidth required
Frequently Asked Questions
Is wgpu the same thing as the browser WebGPU API?
No. WebGPU (lowercase "gpu") is a JavaScript API that lets web browsers access the GPU. wgpu is a separate, native Rust implementation of the same underlying graphics standard — it runs as a standalone application talking directly to Vulkan, Metal, or DirectX 12, with no browser, no JavaScript, and no sandbox involved.
Why does framechart use wgpu instead of a browser?
framechart runs as a DaVinci Resolve plugin, not a web page, so native GPU access via wgpu gives it direct hardware post-processing (bloom, motion blur, anti-aliasing) and frame delivery straight into the Resolve timeline — no browser sandbox, no file export/import round-trip.
What GPU backends does wgpu use in framechart?
Vulkan and DirectX 12 on Windows, Metal on macOS. Rendered frames are then delivered into DaVinci Resolve over CUDA on NVIDIA, OpenCL on AMD/Intel, or Metal on Apple Silicon.
Is my data safe with wgpu rendering?
Yes. Rendering is fully on-device — your GPU processes the animation frames locally, inside DaVinci Resolve. No data is sent to a server. Your CSV data, chart configuration, and rendered frames never leave your computer.
Related Terms & Pages
Last reviewed: July 2026