Hey Product Hunt! 👋 I’m Steve, head of post-production at Studio52, where I’ve run edits and a small post team for 5+ years. What inspired it: clients don’t send hard drives anymore, they send Google Drive links. Every new project started the same way for my team: download hundreds of GB, wait for Media Encoder to make proxies, then shuffle files around before anyone could cut a single frame. We were losing half a day on every job, and every freelancer we hired was dealing with the same thing. The problem I set out to solve: getting from “client shared a folder” to “editing in Premiere” without downloading the footage. With RenderQue, you connect your Google Drive once. Then you drop footage into a watched folder or choose a folder your client shared with you, and Premiere-ready proxies appear in a Proxies folder in your Drive. Your originals never move. How the approach evolved: I started by building it only for myself and tested every proxy in a real Premiere project before anything else. That’s where I learned the details that matter: proxies have to keep the original audio channel layout or relinking breaks, and variable-frame-rate phone footage has to be conformed or it drifts out of sync. Then I opened it up to other editors and learned more. Moving transcoding to the cloud meant no more tying up your own machine. Letting you pick the client folders RenderQue can access, instead of granting access to your whole Drive, was better for privacy. And clear error messages like “ask your client to enable downloads” beat cryptic failures. It works today with H.264, HEVC, ProRes, XAVC, MXF/DNxHD and more. BRAW and R3D are next. I’d love to know: how do you handle proxies for client footage today? I’ll be here all day answering questions. 🎬

RenderQue

Create your proxies in the cloud. Not on your machine.

Create your proxies in the cloud. Not on your machine.