skeet
PricingLog in
skeet

A video editor that has already watched your footage. In the browser, where everyone is.

Product

  • Studio
  • Clive
  • Skeet on the desktop
  • Skeet on a phone
  • Publishing
  • Color
  • Monitoring
  • Audio
  • The schedule
  • Versions and history
  • Keeping a look consistent

Solutions

  • Independent Creators
  • Conversational Media
  • Social Media Pros
  • Streamers
  • Production Studios
  • Founder-Led Content
  • Live Commerce
  • Narrative Film
  • Product & Tech Teams
  • Education & EdTech

Resources

  • Docs
  • Changelog
  • System requirements
  • Learn
  • Community
  • Security
  • Pricing

Company

  • About
  • Contact
  • Careers
  • Brand
Start editing
© 2026 Skeet, Inc.
  • Privacy
  • Terms
  • Cookies
  • Acceptable use
  • Subprocessors
All posts
EngineeringApril 24, 20268 min read

Why we built the GPU Render Engine

The engineering decisions behind rendering and exporting video inside a browser tab.

Traditional video editors are built on legacy CPU-bound architectures. As we moved into the era of 8K raw and agentic assembly, we realized the bottleneck wasn't the AI. It was the render pipeline.

The Worker-Isolated Loop

The engine operates on a Worker-Isolated Rendering Loop, decoupling the UI from the expensive decoding and rendering tasks. This ensures that no matter how heavy the project, the UI remains responsive at a constant 60FPS.

Key Innovations

  • GPU-Native wgpu architecture
  • Zero-Copy Handshake with WebCodecs
  • 96,000 Ticks per second precision