Japanese → Korean
To translate Japanese subtitles to Korean, upload your .srt or .vtt file to SubLingo, pick Korean as the target, and download the translated file with every timecode preserved. Both SRT and VTT are supported, only the cue text is rewritten, and the result drops straight back onto your video in sync.
Last updated: 2026-06-11
Drop your subtitle file here, or click to browse
Supports .srt and .vtt
Drop in your Japanese .srt or .vtt file. SubLingo parses every cue and locks the timings in place.
Set the target language to Korean. The source is auto-detected, so you can leave it on Japanese or let it detect.
Run the translation. Only the text inside each cue is rewritten in Korean — never the timecodes.
Download the Korean subtitle file in the same format you uploaded, ready to drop straight onto your video.
Translating from Japanese into Korean: Korean does use spaces between phrases (eojeol), so line breaks follow those spacing units; Hangul renders as full-width-ish blocks, keeping each line compact. Because only the text inside each cue changes, every timecode from the original Japanese file carries over unchanged.
Need the other direction? Translate Korean subtitles to Japanese.
No. SubLingo translates only the subtitle text, so every start and end time is preserved exactly. Your Korean subtitles stay frame-accurate against the original video.
Yes. Both WebVTT (.vtt) and SubRip (.srt) Japanese files are supported, including multi-line cues. The output keeps the same format you uploaded.
Yes. You can translate a Japanese subtitle file to Korean in your browser for free, with no signup and nothing to install.
You can try it for free with no account. Upload your Japanese file, translate to Korean, and download the result.
Most Japanese subtitle files translate to Korean in a few seconds. Longer files with thousands of cues take a little more, but you stay on the page the whole time.
Typical movie and episode subtitle files — a few hundred KB and a few thousand cues — translate without trouble. Very large files may take longer to process, but the timecodes still come back unchanged.