The short answer
LumaTake supports H.264, HEVC, ProRes 422, and GIF export. Captions can be burned into video or delivered as SRT/VTT sidecar files. Select a preset that fits the destination, then check the exported result before handing it over.
Match the format to the handoff
| Format | Practical use | Before delivery |
|---|---|---|
| H.264 | A finished video for a destination that accepts it | Confirm the destination’s dimensions and file requirements. |
| HEVC | A delivery workflow that supports HEVC | Test playback on the receiving device or service. |
| ProRes 422 | An editing or production handoff | Allow enough storage and transfer time for the output. |
| GIF | A short silent visual loop | Inspect file size and readability; there is no audio. |
The filename alone is not the complete specification. A receiving tool may care about the video encoding, dimensions, frame rate, audio, and subtitle type. Confirm those requirements before rendering a long project.
Keep source quality and export size separate
An export preset can set a larger frame, but it cannot promise to recreate detail missing from the source. Capture readable interface text first. A sharp screen demonstration usually benefits more from a sensible crop and scale than from increasing the output dimensions after the fact.
LumaTake includes match-source, YouTube 1080p/4K, social vertical, LinkedIn 1080p, Slack GIF, and ProRes handoff presets. Check the chosen preset against the actual audience and destination. Recording frame rates and live-stream frame rates are separate settings.
Choose whether captions belong in the picture or beside it
Burned-in captions preserve the visible styling because the words are part of the rendered video. SRT and VTT files keep timed text separate, letting a compatible player or editor decide how to display it. Send both files when the recipient expects a video and a sidecar.
A subtitle file is not an editable video project. It does not carry camera layouts, zooms, color adjustments, or title graphics. Keep the project and media when you expect to revise those elements later.
For generating and correcting the words, use the caption workflow. This page covers the delivery choice after the text is ready.
Inspect the file you are about to send
- Play the beginning, a complex edit, and the final seconds.
- Check narration and system sound through the intended playback device.
- Verify captions at edit boundaries and confirm any sidecar file is present.
- Inspect masked information through motion and transitions.
- Check the file in the destination when possible, including its processed version.
Name the deliverable clearly enough to distinguish the landscape master, vertical cut, and subtitle files. Avoid overwriting the only source project with a final delivery copy.
Questions about this workflow
Should I export subtitles as SRT or VTT?
Use the format accepted by the receiving player, publishing tool, or editor. Both carry timed text; neither promises to preserve every visual caption treatment from the editor.
Does a 4K export make a low-resolution capture sharp?
Not automatically. Choose a readable source and appropriate framing before expecting a larger export to help.
Does the LinkedIn preset publish to LinkedIn?
No. It prepares an export. Account connection and direct publishing are separate features with separate availability.
About this guide
Published by LumaTake, the product described on this site. This guide covers LumaTake’s recording, editing, and publishing workflows. Platform account requirements and supported formats can change.
Try it with your next recording.
Request access to the LumaTake beta for macOS 26 or later. Tell us about the recording or editing workflow you want to improve.
Request beta accessAccount required. Review the subscription offering and privacy policy.