How RenderQue works
The two-minute version of what happens to your footage, what we can and can't see, and the questions editors ask before connecting their Drive.
The problem it solves
Making proxies is the least creative hours of an editor's week: queue everything in Media Encoder, then wait while your machine renders at full fan speed — too laggy to edit on, sometimes too laggy to use at all.
RenderQue moves that rendering to the cloud. Our servers fetch the footage straight from Google Drive at datacenter speed, transcode it with exact Premiere presets, and put the finished proxies back in your Drive. The render step disappears from your machine entirely — and it happens while you're doing something better with your time. Your workflow stays yours: attach the proxies in Premiere exactly as you always have.
What happens to your footage
- Source files stream to a transcode server, are converted, and are deleted immediately after the job. We never keep your media — or your client's.
- Only the small proxy files are written back, into a Proxies folder in your own Drive. Originals are never copied, moved, or duplicated.
- Proxies are named filename_proxy, exactly the way Premiere's own proxy workflow names them, so attaching them is routine.
What we can and can't see
RenderQue uses Google's most limited Drive permission. In plain terms:
- We can read only the files you explicitly pick in the file picker, plus files from public links you paste.
- We cannot browse your Drive, see your other files, or touch anything you didn't point us at.
- Your Google connection is stored encrypted, and you can disconnect it with one click — which also revokes our access at Google's side.
The presets
The three presets match Adobe Premiere Pro's Create Proxies dialog — same containers, bitrates, and audio handling — so proxies behave exactly as editors expect on the timeline.
| Preset | Container | Video | Audio |
|---|---|---|---|
| ProRes QuickTime Proxy | MOV | ProRes 422 Proxy | PCM, source layout kept |
| H.264 QuickTime Proxy | MOV | H.264, 10 Mbps | PCM, source layout kept |
| H.264 MP4 Proxy | MP4 | H.264, 10 Mbps | AAC stereo |
Frame sizes: Full, Half, Quarter, or a custom width × height — just like Premiere. Multi-track audio layouts are preserved, timecode is carried over, and variable-frame-rate sources are conformed so audio never drifts.
Common questions
Does the client need an account?
No. If their link is set to "Anyone with the link", you just paste it. They never sign up for anything.
What about my own private files?
Pick them with the built-in file picker — that's you granting access to those specific files, and nothing else.
What if a file is huge, or Google throttles the link?
Jobs keep their progress. If Google rate-limits a popular link, RenderQue retries automatically and resumes from the exact byte where it stopped, until the file is through.
Can I control the queue?
Pause, resume, or cancel any job at any stage — per file or for the whole queue. Already-proxied files are remembered, so nothing gets transcoded twice by accident.
What does it cost?
RenderQue is free while in beta, and access is invite-only. Paid plans will come later, with clear limits and no surprises.
Something broke — who do I talk to?
Email business@studio52.fm. Beta means your bug reports genuinely shape the product.