LiveStorage

Your Drive folders, translated in place.

Connect a folder and every file inside it — and any subfolder — becomes translatable. Rush Studio pulls the source in, translates it, and lands the output right back in Drive: same folder, formatting intact, nothing to download or re-upload.

Connect Google Drive See it in the dashboard

Two-way syncWatches for new filesDocs · Sheets · Slides · PDF

drive.google.com · Marketing / Q3 Launch

My Drive›Marketing›Q3 Launch Synced

Launch announcement.docxSource

Launch announcement — de.docxNew · German

Launch announcement — ja.docxNew · Japanese

Pricing one-pager.pdfSource

Pricing one-pager — de.pdfNew · German

Feature deck.pptxRe-syncing

A folder in Drive, a project in Rush Studio.

Point us at a folder once. From then on it behaves like any other source — except the files never leave Drive.

Connect a whole folder

Pick one folder and every file inside it, across all subfolders, becomes translatable at once.

Two-way sync

Source files flow in; finished translations flow back to the same folder automatically.

Format-preserving

Docs, Sheets, Slides, and PDFs come back with styles, tables, and layout intact.

Watches for changes

Drop a new file in a watched folder and it's queued for translation without a click.

Connect a folder, not a file

One folder in. Everything comes along.

No more zipping up files or picking them one at a time. Connect a folder and Rush Studio maps everything inside it — every subfolder, every supported file — into a single project. Add a file to that folder next week and it's picked up on the next sync, no setup needed.

Recursive by default

Subfolders come along automatically — the structure is preserved end to end.

Filter what's included

Scope by file type or name pattern so drafts and archives stay out of scope.

Auto-pickup

New files in a watched folder are queued the moment they land.

ReplacesManual file uploads“Which version is latest?” threads

Connect a folder

MarketingWatching

Q3 Launch

Launch announcement.docx

Pricing one-pager.pdf

Blog drafts

How we localize.gdoc

Social

Connect Marketing and all 3 subfolders — 6 files — come along. New files added later are picked up automatically.

Round-trip, not one-way

Translations land right back in Drive.

When a translation is approved, Rush Studio writes it straight back into Drive next to the source — named by language, in the same folder, in the same format. Your team opens Drive and the localized files are simply there. No export step, no re-upload, no drift between systems.

Predictable naming

Outputs follow a pattern you set, e.g. filename — de.docx, so they sort cleanly.

Version-aware

Re-translate after a source edit and the output updates in place — no duplicates.

Permissions respected

Files inherit the folder's Drive sharing — we never widen access.

ReplacesDownload / re-upload cyclesA separate “translated” drive

Two-way sync

Google Drive

Source files

Rush Studio

Translate · review

Pulls source inPushes translations backSame folder, same format

Supported formats

The file types you actually keep in Drive.

Native Google formats and the common office and document types — each round-trips with structure and styling preserved.

DOC

Google Docs

& .docx

XLS

Google Sheets

& .xlsx

PPT

Google Slides

& .pptx

PDF

Text-layer PDFs

TXT

Plain text

.txt, .md

CSV

Row & column data

SRT

Subtitles

.srt, .vtt

JSON

Structured

.json, .xml strings

How it works

Connected in about three minutes.

Authorize with Google

Sign in with Google OAuth and grant access to the folders you choose — nothing more. Revoke any time from Drive or Rush Studio.

Pick folders & languages

Choose the folder to watch and the target languages. Set the output naming pattern and where translations should land.

Translate & sync back

Files flow into your queue, get translated and reviewed, and the finished versions appear back in Drive on their own.

Permissions & security

Scoped access, and nothing you didn't grant.

Rush Studio connects through Google OAuth and only touches the folders you select. Here's exactly what that means.

What we access

The folders you pick. Read source files and write translations back — only inside the folders you connect.

File metadata. Names, types, and modified times, so we know what changed and what to re-sync.

Your Google profile. Name and email, to attribute activity and send sync notifications.

What we never do

Touch other folders. Files outside the folders you connect are invisible to us.

Change sharing. We never widen who can see a file — outputs inherit the source's permissions.

Delete your source. Rush Studio only adds translated files; your originals are never modified or removed.

The details

How the sync behaves.

The fine print teams ask about before they connect a production folder.

Sync direction

Two-way. Source files are read in; approved translations are written back to the same folder.

Sync trigger

New or changed files are detected within minutes of landing in a watched folder. You can also trigger a manual re-sync any time.

Source edits

Editing a source file re-queues just that file. The existing output is updated in place — no duplicate — de copies pile up.

Conflict handling

If someone edits a translated output directly in Drive, Rush Studio flags it and asks before overwriting — your manual edits are never silently lost.

Output location

Same folder as the source by default, named filename — [lang].ext. Optionally route outputs to a separate subfolder per language.

Auth & revocation

Google OAuth 2.0. Disconnect from Rush Studio or revoke from your Google account at any time; access stops immediately.

Questions

Google Drive, answered.

Do the source files ever leave Google Drive?

Only transiently. Rush Studio reads a file to translate it and writes the result back; we don't keep a permanent copy of your source once a project is delivered.

Can I connect a Shared Drive, not just My Drive?

Yes. Shared Drives (Team Drives) are fully supported, and outputs inherit the Shared Drive's membership and permissions.

What happens if I move or rename the connected folder?

The connection follows the folder by its Drive ID, so moving or renaming it in Drive won't break the sync.

Will it translate files added after I connect?

Yes — that's the point of watching a folder. Any supported file dropped in later is queued automatically on the next sync.

How are large folders handled?

Files are queued and translated in batches so a big folder won't overwhelm your queue. You can pause, reprioritize, or scope by file type at any time.

Can two people connect the same folder?

The folder is connected once at the workspace level, so your whole team shares one synced project — no duplicate connections or conflicting outputs.

Keep exploring

Other integrations

Same dashboard, same two-way sync — different tool.

Point Rush Studio at a Drive folder.

Join the waitlist for early-access pricing and a 1:1 onboarding call to get your first folder syncing.

We use cookies

Your Drive folders, translated in place.

A folder in Drive, a project in Rush Studio.

Connect a whole folder

Two-way sync

Format-preserving

Watches for changes

One folder in. Everything comes along.

Translations land right back in Drive.

The file types you actually keep in Drive.

Connected in about three minutes.

Authorize with Google

Pick folders & languages

Translate & sync back

Scoped access, and nothing you didn't grant.

How the sync behaves.

Google Drive, answered.

Other integrations

Figma · Design

GitHub · Code & docs

Dropbox · File storage

Point Rush Studio at a Drive folder.