Private alpha

loopit.video

Send your rushes to text-based editors. They cut. You finish in Premiere.

Windows 11 & Apple Silicon macOS

Get early accessMore for Premiere editors →

Who it's for

Premiere video editors who hand off assembly cuts to journalists, marketers and other subject-matter experts as part of a text-based workflow — then loop it back into Premiere for Rough through to Final Cut.

How it works

  1. 1
    Send from Premiere

    The loopit.video extension packages your rushes and transcript and emails the recipient an invite link.

  2. 2
    Recipient cuts the transcript

    They open the invite from their email, install the free loopit.video desktop app, and edit by selecting transcript text.

  3. 3
    Cut back in Premiere

    Their cut returns as a sequence. The loopit.video extension swaps the proxies back to your full-resolution rushes automatically.

Walkthrough screenshots and a short demo are coming with the public beta. Read the editor walkthrough.

Your files, your cloud, your control

loopit.video is a pointer service, not a storage service. Your rushes, proxies and transcripts travel through your own cloud — Google Drive today, more clouds later. We never hold cleartext of your media or your edits. The recipient's returned cut and their note are end-to-end encrypted on their machine before they reach us, with P-256 ECDH → HKDF-SHA-256 → AES-256-GCM, and decrypted only inside your extension on import.

  • · Rushes, proxies and transcripts stay in your Drive — they never reach our servers.
  • · The return XML and recipient notes pass through our infrastructure encrypted; the plaintext only exists on the recipient's machine and yours.
  • · Recipient access is scoped per project and revocable.

Working with sensitive material? There's a separate Secure Send mode that skips our infrastructure entirely.

▸Secure Send — for sensitive material

Two delivery modes once you've connected your cloud: Server Send (the default) and Secure Send. They differ in where the bundle goes and how the recipient gets it.

Server Send (default)

  • The packaged bundle (proxies + transcript + XML) is uploaded to your Google Drive.
  • It's shared with anyone-with-link permission, scoped per project.
  • The recipient gets an invite email with a link. They click it, the desktop app opens the project, they cut.
  • Convenient — no out-of-band steps. Right for most editorial work.

Secure Send (manual delivery)

  • The bundle is written to a local folder you choose (default: Documents/loopit.video Exports).
  • Nothing is uploaded. No Drive copy, no anyone-with-link share, no project code minted, no manifest POSTed to our servers.
  • You deliver the bundle to the recipient yourself — encrypted USB, secure file-transfer, in-person handover, whatever your security posture requires.
  • The recipient imports the bundle file manually in the desktop app. No invite email is sent.
  • Right for whistleblower interviews, embargoed material, IT-locked-down orgs that can't share via cloud, or any project where the bytes simply can't leave your machine until you decide.

Both modes use the same in-app cutting experience for the recipient. The difference is only in how the bundle gets to them.

Currently in private alpha

Ten hand-picked editors are using loopit.video right now. It's free during alpha. A paid model is coming. Drop your email and tell us what you'd use it for.

One email when alpha opens up. No newsletter, no other use.