Guide · ~9 min read
Browser subtitle tools: privacy, no upload, and when they make sense
Freelancers and creators often search for “online SRT converter” and land on pages that ask you to upload a script. If your dialogue is confidential—or you simply do not want another copy on someone’s disk—browser-local subtitle tools are a better default. This guide explains how they work, what Subtitle Kit does, and how to choose workflows that keep files on your device.
Upload-based vs in-browser processing
Most “free online subtitle” sites follow the same pattern: you pick a file, it travels to their server, they run FFmpeg or a script, and you download the result. That is fine for public YouTube clips. It is a poor fit for unreleased ads, client dubs, or internal training video where the script itself is sensitive.
In-browser tools parse SubRip or WebVTT in JavaScript inside your tab. The shift, merge, or text export happens in RAM on your machine. The static site still loads HTML and JS from a CDN (Cloudflare Pages in our case), but the subtitle bytes are not posted to an application backend for conversion.
What Subtitle Kit is built for
Subtitle Kit is a small set of focused utilities—not a full non-linear editor. Each page does one job well:
- SRT time shift — global offset for sync fixes
- VTT time shift — same idea for WebVTT sidecars
- SRT to text — dialogue for translators
- Line length — vertical video readability
- Read time — voice-over planning from a script
Format helpers such as SRT to VTT and strip HTML tags follow the same local-processing model.
Threat model (plain language)
What you reduce: accidental storage of your .srt on a random SaaS bucket, retention policies you never read, and breach surface on a third-party converter.
What you do not eliminate: someone with access to your unlocked laptop, malware on the device, or a compromised browser extension. Always lock your screen on shared machines and avoid shady extensions that read page content.
What still touches the network: loading the tool page, analytics if you add them later, and any embeds (launch badges, future ads). Read Privacy before relying on the site for regulated data.
How to verify “no upload” yourself
- Open browser DevTools → Network tab.
- Load a tool and process a test SRT.
- Filter by “Fetch/XHR”—you should not see your file posted to an API endpoint.
- Disconnect Wi‑Fi after the page loads; processing should still work until refresh.
This is the same sanity check security-minded editors use before trusting any “online” tool.
When to use desktop or NLE subtitles instead
Stay in Premiere, DaVinci, or Aegisub when you need per-cue ripple edits, style tracks, or frame-accurate spotting across a two-hour film. Use browser utilities for repeatable one-shot fixes: +500 ms after dub export, strip formatting tags before translation, or check whether lines break on 9:16 safe zones.
Many teams combine both: spot in the NLE, export SRT, run a quick browser shift, re-import for delivery.
Translators and agencies
CAT tools and TMS platforms often want plain text, not timing codes. Exporting dialogue via SRT to text locally avoids uploading the whole script to a random “SRT to TXT” site. Pair with SRT to text for translation for workflow tips and QA checks.
Short-form and vertical video
Creators shipping Reels or Shorts care about hook timing and readable line breaks. Privacy still matters when early cuts contain product names or influencer deals. Local line length checks and TikTok line length guidance keep that pass on-device before you upload video to a platform—not your .srt to a stranger’s server.
Checklist before you trust any online subtitle site
- Does the FAQ say files are uploaded? If yes, assume retention.
- Is there a privacy policy and contact?
- Can you use the tool without creating an account?
- Does processing work with network disabled after load?
- Is the output format correct (comma vs dot milliseconds for SRT vs VTT)?
Open Subtitle Kit tools (free)
How to use
- Pick a task: shift timing, export text, check line length, or estimate read time.
- Open the matching tool on Subtitle Kit—no sign-up.
- Load or paste your file; confirm nothing is sent to a server (network tab optional).
- Download the result and continue in your NLE or translation CAT tool.
Frequently asked questions
- Do browser subtitle tools upload my SRT file?
- Subtitle Kit runs in your browser with JavaScript. Your .srt or .vtt is read from memory on your device—we do not send subtitle content to our servers for conversion or shifting.
- Are client-side subtitle tools safe for NDA scripts?
- Local processing reduces exposure compared to upload-based converters. You still share metadata with your browser vendor and CDN when loading the page; for strict NDAs, use air-gapped desktop tools. For everyday freelance work, browser-local is a practical middle ground.
- What data does Subtitle Kit collect?
- The tools themselves do not require an account. Hosting (Cloudflare Pages) may log standard HTTP requests like any static site. See the site privacy page for details; subtitle file contents are not uploaded for processing.
- Why not use a desktop app instead?
- Desktop apps are great for heavy timelines. Browser tools win when you need a quick offset, text export, or line-length check on a laptop without installing software—or when IT locks down installs.
- Can I use these tools offline?
- You need to load the page once. After that, processing works offline in many browsers until you refresh. For fully offline workflows, save the site or use a dedicated desktop subtitle editor.
- Is local processing slower than server conversion?
- For typical SRT files (hundreds of cues), in-browser shifts are instant. Very large files may take a second or two—still faster than uploading to a remote API and waiting in a queue.