Send the video or a link and download Arabic SRT and VTT files with cues from word-level timings. Arabic speech comes back as Arabic cue text. Want the transcript on its own? That page covers it. Nothing to pay for the first recording up to 3 hours; then $8 for 1,000 minutes.
Three steps
No install, and no manual timecoding.
A video file, an audio file or a link. Larger recordings continue on the upload page, up to 10 hours or 5 GB.
Each word carries its own timing. Proper nouns and any Latin-script brand names inside the speech are worth checking here.
SRT for editors and platform uploads, VTT for browser players, along with TXT, DOCX, JSON and MD.
Captioning Arabic
Arabic runs right to left, and a subtitle file stores the characters in logical order while the player is responsible for laying them out. Most modern players do this correctly. Older ones, and some editing suites, do not: the classic symptom is a line that reads correctly until a full stop or a question mark jumps to the wrong end. That is a rendering problem rather than a problem with the file, and the fix is a player or a caption renderer with proper bidirectional support.
Mixed direction inside one line is where it gets sharper. A sentence in Arabic that contains an English product name, a URL or a Western-digit figure has runs going both ways, and the placement of the punctuation between them depends on the renderer. If your video mixes technical English into Arabic speech, preview those specific cues rather than assuming the whole file is fine.
Caption downloads hold cue text and timings only, so no line starts with a name even in a multi-voice recording. The transcript view shows who is speaking, and the JSON export from the same job carries the structure.
Delivery
Sidecar tracks, platform uploads and burned-in text.
Attach the SRT as the Arabic track in Studio. Uploaded cue files render right-to-left properly and are indexed for search.
Burned-in text needs an editor that shapes Arabic and handles direction. Import the SRT and check one cue on screen before the full render.
Both accept SRT onto a caption track. Arabic shaping depends on the font and the title engine, so test early in the Resolve setup.
VTT through an HTML5 track element inherits the browser text engine, which handles bidirectional text well. Start from the published link instead of moving the master.
Pricing
A pack from $4 opens the full transcript, caption exports included. Beyond that the packs are one-time: $8 for 1,000 minutes, $12 for 2,000 minutes, $24 for 5,000 minutes, with credits that never lapse.
| Arabic video | $8 pack | $12 pack | $24 pack |
|---|---|---|---|
| 20-minute news segment | $0.16 | $0.12 | $0.10 |
| 55-minute lecture | $0.44 | $0.33 | $0.26 |
| 120-minute broadcast | $0.96 | $0.72 | $0.58 |
Values are the share of one pack each recording consumes. All formats are included — the pricing page has the rest.
FAQ
Arabic. Captions are written in the language that was spoken, so Arabic audio gives Arabic cue text, and nothing is converted into another language.
Usually not. The file stores characters in logical order and the player lays them out; a renderer without proper bidirectional support misplaces the punctuation.
They create a left-to-right run inside a right-to-left line. Preview those cues specifically, because renderers differ in where they place the surrounding punctuation.
Yes, the mirrored forms ، and ؟ are written into the cue text where they belong.
No. Speaker separation lives in the transcript view on screen and in the JSON export; the caption formats hold cue text and timings.
Speech is written as it is said, whether it leans formal or dialectal, without a separate setting to choose.
Instant preview, no account required. A first recording of as much as 3 hours is free.