Skip to content
CutConvert
Post-production file converter

Convert JSON to SRT subtitles

Turn timed transcripts or YouTube chat replay JSON/JSONL into SRT. Preview the detected captions, or map text and timestamp fields in a custom JSON export.

Convert your files

Drop files here

browseWhisper or transcript JSONConverted in your browser. Files never leave your device.About an hour of footage is free. Larger files: $3 each, or Pro $9/month for everything up to 50 MB.

up to 2 files · 2 MB each

free to start · project to project: $5 · every other conversion: $3 · Pro $9/month · pricing

Converting as a guest. A free account has no monthly cap on files within the free size limit.

Queue
0/2
No files queued yet — drop something above to begin.

Como converter JSON para SRT

Converta JSON para SRT online. O CutConvert lê transcrições do Whisper — verbose_json da OpenAI, saída do whisper.cpp — e JSON genérico de segmentos com tempos, e gera legendas SRT limpas e numeradas, com falantes preservados.

  1. Adicione seus arquivos JSON

    Arraste seus arquivos .json do Whisper ou de transcrição para a área de upload, ou clique para procurar.

  2. Converta JSON para SRT

    Clique em Converter. Cada segmento com tempo vira um bloco SRT com temporização em milissegundos; campos de falante viram identificações.

  3. Baixe o resultado

    Baixe o arquivo convertido na hora — ou um único arquivo ZIP quando você converte um lote de arquivos.

JSON de transcrição e Legendas SRT, explicados

A transcrição por IA gera JSON; players e editores querem SRT. Este conversor aceita os formatos que existem de verdade por aí: verbose_json do OpenAI Whisper (segmentos com início/fim em segundos), whisper.cpp (arrays de transcrição com offsets em milissegundos) e arrays genéricos de segmentos {start, end, text}. A temporização é lida do arquivo — nunca estimada.

Transforme verbose_json do Whisper, saída do whisper.cpp ou qualquer JSON de transcrição com tempos em legendas SRT limpas. É grátis para começar, criptografado em trânsito e converte um lote inteiro em um único ZIP — faça login quando precisar de trabalhos grandes e de alto volume.

Perguntas frequentes sobre JSON para SRT

Quais formatos de JSON são suportados?

verbose_json do OpenAI Whisper (um array segments com início/fim em segundos), saída do whisper.cpp (um array transcription com offsets ou timestamps) e arrays genéricos de objetos {start, end, text} — com campos opcionais de falante, em segundos ou milissegundos.

Como obtenho o verbose_json do Whisper?

Na API da OpenAI, defina response_format como verbose_json. Rodando o Whisper localmente, a saída .json padrão funciona; o arquivo gerado com --output-json do whisper.cpp também.

Meu JSON só tem um campo de texto simples — dá para converter?

Não. O SRT precisa de tempos de início e fim por segmento, e uma transcrição de texto puro não tem nenhum. Exporte novamente com temporização por segmento (verbose_json no Whisper) e a conversão funcionará.

As identificações de falantes vindas da diarização são mantidas?

Sim — segmentos que carregam um campo speaker saem como blocos SRT identificados, então transcrições diarizadas continuam atribuídas.

E se meu arquivo for um JSON de transcrição do Premiere Pro?

Use o conversor de transcrição do Premiere para SRT em /prtranscript/srt — ele lê o formato de transcrição do Premiere (incluindo arquivos .prtranscript binários) diretamente.

Guias para este fluxo de trabalho

Mais conversores

Why editors trust it

Free to start

Convert everyday batches for free. Create an account when you need large, high-volume jobs.

Batch in, one ZIP out

Convert a batch within your allowance and download a single ZIP, or one file if that is all you need.

Made for editors

Whole timelines from Premiere, Final Cut and Avid with transitions, markers, titles, keyframes, levels, nests and bins; captions that keep their italics, colour, placement and speakers across SRT, VTT, ASS, TTML, iTT, SCC and STL, any of them in, any of them out; transcripts into Premiere with the words the engine timed. Frame rates and timecode handled the way post expects.

Private by design

Files are converted in your browser. Queued files can be saved locally to restore your job after checkout. Conversion metadata helps us diagnose errors; file contents are not uploaded.

Questions, answered

Where are my files processed?

In your browser. The converter runs on your own machine and the file never leaves it; the site only records that a conversion happened. CutConvert never sees, stores, sells or shares your media.

Is it free? Do I need an account?

About an hour of footage per file is free, on every converter: 100 KB of subtitles or captions, 500 KB of Word transcript, 2 MB of transcript JSON, 1 MB of Resolve project, 5 MB of Final Cut XML, with Premiere projects and Avid AAF a little under the hour. Guests get five conversions a month, a free account has no monthly cap within those sizes, and above that project-to-project transfers are $5 per file. Every other conversion is $3, including project files to captions, reports or cut lists, and captions or transcripts into an editor. Pro is $9 a month ($90 a year) for every file type up to 50 MB; Studio is $19 a month ($190 a year) for files up to 500 MB. Paid-file access lasts 24 hours.

What do I get when I convert multiple files?

Drop several files and you get back one ZIP archive containing every converted file. Convert a single file and you get that one file back, no ZIP. Tick extra formats under the output chips and the same ZIP carries every one of them, and a file counts as one conversion whatever it is written to.

Which formats are supported?

Timelines: Premiere .prproj, DaVinci Resolve .drp (as exported, or gzip- or Zstandard-wrapped), Avid AAF and Final Cut FCPXML in; FCP7 XML, FCPXML, Resolve .drp, CMX 3600 EDL and shot-list CSV out. A Premiere or Final Cut edit travels with its transitions, markers, titles, opacity and scale keyframes, clip volume, speed changes, nested sequences, bins, audio channel routing and each file's own frame rate, wherever the output has a place for them; an Avid AAF brings its transitions, markers, clip levels with their keyframes, muted tracks, nested stacks and each clip's own rate. Captions and transcripts, read and written: SRT, WebVTT, SBV, ASS, TTML, DFXP, iTT, SCC, MCC (a second 608 channel comes out as its own file), EBU-STL, Avid caption TXT, CapCut drafts of any size, timed CSV, Word, plain text, Whisper, WhisperX, AssemblyAI, Deepgram, Rev.ai and CapCut JSON, TwitchDownloader chat logs as a chat replay, Premiere transcript JSON and .prtranscript, Rev, Otter and Word-style transcripts, with italics, colour, placement and speakers kept where the output can hold them and measured word timing into Premiere. EDLs become event CSV reports. The capability table lists what every pair keeps.

Can I pick a frame rate?

Yes. For EDL and Avid caption output you can choose 23.976, 24, 25, 29.97, or 30 fps, or let CutConvert auto-detect it from your source.