Add your LRC file
Drop one or more .lrc 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 .lrc file to .smi 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 .lrc file to .smi extracts the document's content from its office package into a portable form. A .lrc file is a synchronized lyric document: each line is prefixed with a [mm:ss.xx] timestamp so a music player can highlight words in time with a song. Unlike caption formats, an .lrc line stores only a start time, with its end implied by the next timestamp.
An .smi file is a SAMI caption document: HTML-like markup in which <SYNC Start=…> elements mark the millisecond at which a caption appears, and the caption runs until the next SYNC. Microsoft designed it as an accessibility format, so a single file can carry several languages selected by CSS class. For this route the practical draw is several language tracks in one file, chosen by class and plain text and editable anywhere — balanced against never formally standardised, so real-world files vary in structure, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .lrc, stores only start times, so line durations must be inferred on conversion. Switching to .smi buys you several language tracks in one file, chosen by class, which is why it is the better fit for captioning legacy Windows Media and Silverlight content. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | LRC synced lyrics (.lrc) | SAMI captions (.smi) |
|---|---|---|
| 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 | each timed line begins with one or more [mm:ss.xx] tags; the fraction is usually centiseconds | the document has an HTML shape: <SAMI> wrapping <HEAD> with a <STYLE> block and <BODY> with the SYNC elements |
| Strongest at | displaying scrolling, time-synced lyrics in a music player | captioning legacy Windows Media and Silverlight content |
| Weak spot | stores only start times, so line durations must be inferred on conversion | never formally standardised, so real-world files vary in structure |
Drop one or more .lrc 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 .smi in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if SMI 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 SMI file. Outputs keep the original filename with the .smi extension.
There is no visual quality to lose — lrc is text-oriented and smi 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 .lrc 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.
Windows Media Player, VLC, PotPlayer, and MPC-HC read .smi, and Subtitle Edit converts it. Browsers do not. Novus Convert parses the SYNC blocks locally with document types and external entities refused and script and style content removed before any text is read, then writes any of the twelve timed-text targets.
It depends on the content: the document has an HTML shape: <SAMI> wrapping <HEAD> with a <STYLE> block and <BODY> with the 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 .lrc → .smi → .lrc is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.