Private alpha

textbased.video

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

Windows · macOS (Apple Silicon)

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 textbased.video extension packages your rushes and transcript. By default it uploads the bundle to your own Google Drive and emails the recipient an invite link. (Or use Secure Send to skip the cloud entirely and deliver the bundle yourself.)

  2. 2
    Recipient cuts the transcript

    The recipient installs the free textbased.video desktop app and opens the bundle — either via the invite email link, or by opening a Secure Send file you delivered. They edit by selecting transcript text.

  3. 3
    Cut back in Premiere

    Their cut returns as a sequence. The textbased.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

textbased.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 — and never reach our servers. What does live on our servers is the pointer plumbing that makes the handoff work: a short project code (8 characters) that we mint and that both your extension and the recipient's app use to find the right project, the Drive folder ID it points at, and (Server Send only) the recipient's email address so we can send the invite. The recipient's edit XML and any note they typed are end-to-end encrypted on their machine before reaching us, and decrypted only inside your extension on import. The full cryptographic detail and our list of sub-processors is in the privacy policy.

  • · Rushes, proxies and transcripts stay in your Drive — they never reach our servers.
  • · What we DO hold on our servers: project codes, Drive folder pointers, recipient email addresses (Server Send only), and the encrypted return ciphertext (until you import it).
  • · The return XML and the recipient's note pass through our infrastructure encrypted; the plaintext only exists on the recipient's machine and yours.
  • · A small cleartext metadata strip travels alongside each encrypted return — project code, edit name, cut count, sequence runtime, timestamps — so your extension can tell edits apart at a glance without decrypting first.
  • · Recipient access is scoped per project code and revocable from the editor's dashboard.

Working with sensitive material? Pair Secure Send (no cloud upload on the send path; you deliver the bundle yourself) with the desktop app's Export XML button (no upload on the return path either). Together they keep every byte of your project off our servers.

▸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/textbased.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

We need some alpha users right now. It's free during alpha. A paid model is coming. Drop your email and tell us what you'd use it for.

By submitting, you consent to textbased.video holding your email address and use-case answer for the sole purpose of contacting you when the alpha opens up. We will send one email. We do not send newsletters, share your address with third parties, or use your data for advertising. We keep your record until you ask us to delete it, or up to 12 months after the paid launch — whichever comes first. To withdraw consent or have your record deleted at any time, email support@textbased.video. Full details in the privacy policy.

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

textbased.video is in private alpha. The Premiere extension and the desktop app are not currently signed, verified, or certified by Google, Microsoft, or Apple — Google's Drive OAuth verification is queued for submission (the alpha cohort sees an “unverified app” consent screen on sign-in), Windows SmartScreen warns “Unknown publisher” on first install, and macOS Gatekeeper warns “unidentified developer”. Vendor certifications and signed installers arrive with the paid launch. See Privacy and Terms for the full picture.