Add your SRT file
Drop one or more .srt files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting a .srt file to .sami extracts the document's content from its office package into a portable form. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting a .srt file to .sami extracts the document's content from its office package into a portable form. A .srt file is a SubRip subtitle document: numbered cues with start and end timestamps and plain caption text. It is the most common caption sidecar for video players, editors, and streaming toolchains that need a simple, widely understood text format.
A .sami file is the same Synchronized Accessible Media Interchange caption document as .smi, written with the long form of the extension. The contents are identical — <SYNC Start=…> elements inside an HTML-like SAMI document — and the long extension is chosen mainly to avoid colliding with SMIL files, which also claim .smi. For this route the practical draw is unambiguous about which format the file actually is and identical tooling support to .smi wherever SAMI is recognised — balanced against some players recognise only .smi and must be given a renamed copy, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .srt, no standard support for advanced styling, voices, or regions. Switching to .sami buys you unambiguous about which format the file actually is, which is why it is the better fit for storing SAMI captions where .smi would collide with SMIL files. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | SubRip subtitles (.srt) | SAMI captions (.sami) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | cues are blocks of an index, a timecode arrow line (HH:MM:SS,mmm --> HH:MM:SS,mmm), one or more text lines, and a blank separator | byte for byte the same format as .smi: <SAMI>, <HEAD> with a <STYLE> block, and <BODY> with SYNC elements |
| Strongest at | delivering captions alongside MP4 or MKV downloads | storing SAMI captions where .smi would collide with SMIL files |
| Weak spot | no standard support for advanced styling, voices, or regions | some players recognise only .smi and must be given a renamed copy |
Drop one or more .srt files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .sami in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if SAMI is selectable, the route is real and validated.
Press Convert. The package is unzipped in memory and its XML content parsed locally; nothing is uploaded.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid SAMI file. Outputs keep the original filename with the .sami extension.
There is no visual quality to lose — srt is text-oriented and sami is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Yes — the .srt file is processed inside your browser tab and never uploaded. The package is unzipped in memory and its XML content parsed locally; nothing is uploaded. Close the tab and the file is gone from memory.
Players that read SAMI generally accept .sami as well, though a few match on .smi alone. Novus Convert treats the two identically, running the same hardened SAMI parser — no document types, no external entities, script and style content stripped — and exports any of the twelve timed-text targets.
It depends on the content: byte for byte the same format as .smi: <SAMI>, <HEAD> with a <STYLE> block, and <BODY> with SYNC elements. Convert one representative file first and compare before batch-processing a large set.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .srt → .sami → .srt is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.