# DaVinci Resolve Export Settings for Twitter (X) in 2026

> **Quick answer:** DaVinci Resolve's export settings for Twitter (X): MP4, H.264, AAC audio, and your timeline's native resolution (1920x1080, 1080x1080, or 1080x1920). Non-Premium accounts are capped at 140 seconds and 512 MB; Premium subscribers get hours-long runtimes, up to 8 GB, and 4K. Resolve ships a built-in Twitter preset.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-08-02 · DaVinci Resolve 21.0.2 (July 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-export-settings-for-twitter-x*

You typed "DaVinci Resolve export settings for Twitter (X)" because the platform changed its name, its file size caps, and its Premium tiers since the last time you exported for it, and you want the current numbers, not a 2022 forum post. Fair. As of August 2026, running DaVinci Resolve 21.0.2, here's the whole spec, sourced from X's own help center and its ad platform, matched to the exact fields on the Deliver page.

This is a reference page, not an essay. Skim the tables, find the row that matches your account and your content, and copy the numbers into Resolve. If you need the deeper mechanics too, the encoder settings, the color and frame rate traps, the caption workflow, the API's separate limits, and a couple of worked examples, they're further down.

## What Are X's Official Export Specs for a Regular Post?

X publishes one spec sheet for ordinary posts, whether you're on the free tier or an X Premium subscriber, and the codec and container never change between tiers. What changes is duration, file size, and playback resolution, covered in the next section.

| Setting | X's specification |
| --- | --- |
| Container | MP4 or MOV |
| Video codec | H.264, Baseline, Main, or High profile |
| Chroma subsampling | 4:2:0 |
| Audio codec | AAC, Low Complexity (LC) profile |
| Audio channels | Mono or stereo (no 5.1 or greater) |
| Audio sample rate | 44.1 kHz or 48 kHz |
| Audio bitrate | 128-320 kbps |
| Video bitrate | 5,000-25,000 kbps |
| Frame rate | Up to 60 fps; 30 or 60 fps recommended |
| Recommended resolution | 1280x720 (landscape), 720x1280 (portrait), 720x720 (square) |
| Aspect ratio | 16:9, 9:16, or 1:1 |

Source: [X Developer Platform's Media Best Practices](https://developer.x.com/en/docs/x-api/v1/media/upload-media/uploading-media/media-best-practices) and [X Help Center's video guide](https://help.x.com/en/using-x/x-videos).

**A DaVinci Resolve export for Twitter (X) is MP4, H.264, AAC, at your timeline's native resolution, the same recipe as a YouTube export with different bitrate and duration numbers attached to it.** If you already export for YouTube from this site's [YouTube export settings guide](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-export-settings-youtube), the codec side of this page will feel familiar. The limits are what's different, and they're the whole reason this guide exists.

## How Do You Set These on DaVinci Resolve's Deliver Page?

Open the Deliver page, the rocket icon at the bottom of Resolve, and build the export from Resolve's own Twitter preset or from scratch.

1. In Render Settings, select the **Twitter** preset, or set **Format** to MP4 and **Codec** to H.264 manually.
2. Confirm **Single clip** is selected and the range dropdown above the timeline reads **Entire timeline**, not In/Out range.
3. Leave **Resolution** and **Frame rate** on your timeline's native values. Don't upscale a 1080p edit to 4K just because X now accepts it; X still re-encodes whatever you send.
4. Set **Quality** to **Restrict to** and enter a bitrate between 5,000 and 25,000 kbps, matched to your resolution and how much motion is in the shot (see the bitrate table further down).
5. In the **Audio** tab, set the codec to **AAC**, sample rate **44.1 kHz** or **48 kHz**, and confirm you're exporting mono or stereo, not a 5.1 mix.
6. If your timeline has a subtitle track, tick **Export Subtitle** and choose the separate SRT file option, not burn-in.
7. Click **Add to Render Queue**, then **Start Render**.
8. Open the three-dot menu in Render Settings and choose **Save New Preset**. Name it something like "X 1080p master" so it's one click next time.

Quick Export, the lightning-bolt icon next to the rocket, offers the same Twitter preset in a smaller dialog with fewer fields to double-check. Use it for a fast turnaround post where you trust the preset's defaults. Use the full Deliver page, with its Restrict to bitrate field and its Advanced Settings, for anything going to a client, a brand account, or an ad campaign, where a wrong setting costs more than a re-render.

## Non-Premium vs Premium vs Premium+: Which Limits Apply to You?

Duration and file size are where X's tiers actually diverge, and this is the table most editors skip until an upload gets rejected.

| Account type | Max duration | Max file size | Resolution ceiling |
| --- | --- | --- | --- |
| Non-Premium (free) | 140 seconds (2:20) | 512 MB | 720p playback |
| Premium ($8/month) or Premium+ ($40/month) | Roughly 2 hours at 1080p | 8 GB | 1080p |
| Premium or Premium+, longer form | Up to about 4 hours | 16 GB | 720p only past the 2-hour mark |
| Premium or Premium+, 4K | Up to 60 fps | Same as the 1080p tier above | 3840x2160, web and iOS only |

Sources: [X Help Center's video guide](https://help.x.com/en/using-x/x-videos), [X Help Center's longer videos page for Premium subscribers](https://help.x.com/en/using-x/premium-longer-videos), and [X Help Center's About X Premium page](https://help.x.com/en/using-x/x-premium).

**A non-Premium account on X can upload a video up to 140 seconds long and 512 megabytes in size, while a Premium subscriber can upload something hours long and gigabytes bigger from the exact same Resolve export settings.** The codec never changes. What changes is whether the account attached to the upload has a subscription.

If you're exporting for a client or a brand account and you're not sure which tier applies, ask before you build a 4K master. A non-Premium account will simply reject a file over 512 MB or a runtime past 140 seconds, and there's no error message that tells you which limit you hit first.

## Does DaVinci Resolve's Built-In Twitter Preset Still Match X's Current Specs?

Mostly, and it's worth checking rather than assuming. Resolve's Deliver page and its Quick Export window both ship a preset for the platform, alongside YouTube, Vimeo, TikTok, and Dropbox, per [Blackmagic's own reference manual section on render presets](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part3929.htm).

**DaVinci Resolve's export preset is still labeled Twitter, not X, years after the platform's rebrand, and that label mismatch is a useful reminder to check the preset's actual settings instead of trusting the name.** The preset gives you a fast, correctly-coded starting point, MP4 container and H.264 video, but presets don't know your account tier and they don't know whether you're posting a 15-second teaser or a 3-minute clip that needs Premium's longer runtime. Open the preset, confirm its resolution matches your timeline, and set Quality to Restrict to with a bitrate from the table in this guide rather than leaving it on whatever the preset defaulted to.

The honest comparison point here is Facebook and LinkedIn, which get no built-in preset in Resolve at all, so every export for those platforms is a custom H.264 job from scratch, a workflow covered in our [LinkedIn export settings guide](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-export-settings-for-linkedin-video). X at least gets you most of the way there with one click.

## Does DaVinci Resolve Free Change Any of These Export Settings?

No, not for X. That's the short answer, and it's worth stating plainly, because the free-vs-Studio split trips people up constantly for other delivery destinations that need more than X actually asks for.

Blackmagic draws the line at bit depth, frame rate ceiling, and resolution, not codec support. The free version "works with virtually all 8-bit video formats at up to 60fps in resolutions as high as Ultra HD 3840 x 2160," while Studio adds 10-bit output, frame rates up to 120fps, and resolutions beyond 4K, per [Blackmagic's own version comparison page](https://www.blackmagicdesign.com/products/davinciresolve/compare). Every number in that free-tier ceiling, 8-bit, 60fps, 3840x2160, sits inside or exactly at what X actually accepts. X's own spec tops out at 60fps and, for Premium accounts, 3840x2160 4K. There's no gap for a free-version user to fall into.

**A free copy of DaVinci Resolve can produce every export in this guide, from a 720p organic post to a 4K Premium upload, without hitting a single Studio-gated resolution or frame rate limit.** Where Studio earns its price on an X export specifically isn't the codec or the resolution ceiling, it's speed. Hardware-accelerated H.264/H.265 encoding is a Studio-only feature on Windows and Linux, so the free version falls back to a slower, CPU-bound encode path on those platforms. On Mac, the gap is usually smaller, since Apple Silicon's media engine handles H.264/H.265 encoding at the hardware level regardless of which version of Resolve is doing the exporting.

If you're on Resolve Free and a 4K export for a Premium X account is taking longer than you'd like, that's a hardware-encoding question, not a spec question. Dropping your export resolution to 1080p, which plays back identically for the roughly half of X's audience without Premium anyway, shortens the render without costing quality anyone but a Premium subscriber on a large screen would notice.

## Should You Set a Keyframe Interval or Other Advanced Encoder Settings for X?

Neither X's help center nor its developer documentation publishes a required keyframe interval, so you're not violating a spec by leaving Resolve's defaults alone. But the option exists on the Deliver page, and knowing what it does keeps you from guessing when an upload looks softer than the export you rendered.

Open the gear icon next to **Advanced Settings** in Render Settings, on the H.264 or H.265 codec panel, and you'll find a **Key Frame Every** field, measured in frames, along with a **B Frames** count. A keyframe, or I-frame, is a complete image the encoder can rebuild from scratch; everything between two keyframes is calculated as a difference from its neighbors, which is how H.264 gets its file size down. A shorter keyframe interval means more full images per second of video, which helps a viewer who scrubs or a platform that re-encodes aggressively, at the cost of a slightly larger file at the same quality setting.

**A two-second keyframe interval, 48 frames at 24fps or 60 frames at 30fps, is standard practice across most web and broadcast delivery pipelines, not a Twitter-specific rule.** That guidance comes from general encoding practice, not from X directly, since X's own spec pages are silent on GOP length, per [Haivision's rundown of encoding fundamentals](https://www.haivision.com/blog/all/video-encoding-best-practices-6-practical-tips-for-optimizing-latency-bandwidth-and-picture-quality/). Leaving Resolve's default keyframe interval alone is fine for almost every X export; only touch it if you're troubleshooting a specific playback issue, like a video that looks blocky right after a scene change, which a shorter interval sometimes fixes.

One setting that does matter more directly: leave **B Frames** at Resolve's default rather than maxing it out. B-frames compress harder but take longer to decode, and a platform re-encoding your upload on ingest gets more predictable results from a file that isn't already pushed to the edge of the H.264 spec.

## Should You Tag Your Export's Color Space for X?

Yes, and this is the export mistake that produces a video that looks correct in Resolve's viewer and washed out or oversaturated the moment it's live on X.

X doesn't publish a required color space tag the way it publishes bitrate ranges, so you won't find this in any official spec sheet. That silence is exactly the problem: web video players, including whatever renders inside the X app, generally assume standard Rec.709 with an sRGB-like gamma curve unless a file's metadata says otherwise, and DaVinci Resolve gives you more than one way to tag a Rec.709 export.

In the Deliver page's **Advanced Settings**, under the video section, the **Color space tag** and **Gamma tag** dropdowns control what your rendered file tells the next piece of software about how to interpret its pixels. If your timeline's color science is Rec.709, the default for most non-color-managed projects and the safe target after grading in DaVinci Wide Gamut and converting out with a Color Space Transform, leave both tags on **Same as Project** or set them explicitly to Rec.709. What trips editors up is exporting a Rec.709 Gamma 2.4 file and having a platform's player reinterpret that gamma curve as something closer to sRGB, which crushes shadows or lifts them depending on which direction the mismatch runs.

**A DaVinci Resolve export that looks correct in the Deliver page's preview and washed out on X almost always has a color space or gamma tag mismatch, not a bitrate problem.** If you're grading in a wide color gamut and converting to Rec.709 only at the end of your node tree, double check that the Deliver page's tags match what you actually rendered, not what your timeline setting defaulted to. This isn't an X-specific quirk; the same mismatch produces the same washed-out result on YouTube, LinkedIn, and any other platform that re-encodes what you send it. X just doesn't warn you about it anywhere in its documentation the way some competitors' upload flows do.

If everything downstream of your grade, monitor, timeline, and export tag is already set to plain Rec.709 Gamma 2.4, you can skip this section and export. This mistake only bites the workflows that grade in a wider space and convert late, or that mix footage graded on two different machines with different default tags.

## What Are X's Video Ad Specs, and How Are They Different From a Regular Post?

Different enough that reusing an organic export for a campaign is the fastest way to get a Campaign Manager upload rejected, and "video ad" on X isn't one format. It's several, each with its own dimensions.

### In-feed and timeline video ads

The default placement, the one that looks like an organic post with a Promoted label attached.

| Setting | Organic post | In-feed video ad |
| --- | --- | --- |
| Container | MP4 or MOV | MP4 or MOV |
| Video codec | H.264, 4:2:0 | H.264, Baseline/Main/High, 4:2:0 |
| Audio codec | AAC LC | AAC LC |
| File size | 512 MB (non-Premium) to 16 GB (Premium) | 1 GB, flat, regardless of tier |
| Duration | 140 sec (non-Premium) to ~4 hours (Premium) | Up to 140 sec technically; 15 sec or less recommended |
| Resolution | Up to 1080p or 4K (Premium) | 1920x1080 max; 1280x720 recommended |
| Frame rate | Up to 60 fps | Up to 60 fps; 30 fps recommended |
| Bitrate | 5,000-25,000 kbps | 6,000 kbps recommended at 1080p; 5,000 kbps at 720p |

Sources: [X Business's creative ad specifications](https://business.x.com/en/help/campaign-setup/creative-ad-specifications) and [X Developer Platform's Media Best Practices](https://developer.x.com/en/docs/x-api/v1/media/upload-media/uploading-media/media-best-practices).

### Video Website Card ads

A card that pairs a video with a click-through button, used for traffic and conversion campaigns rather than pure awareness.

| Setting | Video Website Card |
| --- | --- |
| Aspect ratio | 1:1 |
| Recommended resolution | 1200x1200 |
| File size | 1 GB, same flat ad cap |
| Duration | Same 140 sec technical ceiling, 15 sec recommended |

For comparison, an image Website Card asks for a 1.91:1 image at 800x418, which is the number you'll see if you're building a static companion card for the same campaign, per [DoChipo's rundown of X's ad specs](https://www.dochipo.com/twitter-ad-size/). If you're cutting a square export for a Website Card in Resolve, set your timeline's Custom resolution to 1200x1200 before you edit, the same discipline as any square export, not after.

### Carousel video ads

Two to six cards in a single unit, each one a video or an image.

**Every card in an X carousel ad has to share the same aspect ratio; mixing a 1:1 card with a 1.91:1 card in one carousel gets the whole unit kicked back**, per [DoChipo's ad specs guide](https://www.dochipo.com/twitter-ad-size/). If a client hands you five clips at different crops for one carousel, that's not a Resolve settings problem, it's a pre-edit conversation: pick one aspect ratio, square is the safest default since it holds up on both mobile and desktop, and reframe every card to match before you touch the Deliver page.

### Amplify Pre-roll ads

A different beast entirely: a short ad that plays before video content from a publisher partner, rather than in the main feed.

| Setting | Amplify Pre-roll |
| --- | --- |
| Aspect ratio | 1:1 recommended |
| Resolution | 1200x1200 recommended, 600x600 minimum |
| File size | 1 GB |
| Duration | 6-15 seconds ideal; 140 sec technical maximum |
| Frame rate | 29.97 or 30 fps |
| Bitrate | 6,000 kbps at 1080p; 5,000 kbps at 720p |
| Captions | Strongly recommended, since publisher overlays and countdowns cover part of the frame |

Source: [Tweetfull's guide to X Amplify Pre-Roll ads](https://tweetfull.com/blog/twitter-pre-roll-specs-complete-guide-to-x-amplify-pre-roll-ads/), corroborated against [X Business's creative ad specifications](https://business.x.com/en/help/campaign-setup/creative-ad-specifications).

**X's video ads are capped at 1 gigabyte no matter which account is running the campaign, which is a tighter ceiling than a Premium subscriber's organic upload gets.** Build to the ad spec from the start if there's any chance the post gets boosted later, the same logic that applies on LinkedIn's ad platform.

Amplify Pre-roll adds one more wrinkle beyond aspect ratio: publisher overlays sit in the top-left and bottom-right or bottom-left corners of the frame for previews and countdowns. Keep key visuals, logos, and any burned-in text away from those corners, since a caption or brand mark that lands under a publisher's countdown timer defeats the point of putting it there. If you're building a pre-roll placement specifically, set your timeline to a square Custom resolution before you edit, not just before you export.

### Which ad format am I actually building?

| If your ad is... | Use this format's specs |
| --- | --- |
| A boosted version of a normal post | In-feed video ad |
| A "learn more" or "shop now" click-through | Video Website Card |
| Multiple products or angles in one swipeable unit | Carousel video ad, one aspect ratio for every card |
| Playing before someone else's video content | Amplify Pre-roll |

## Which Aspect Ratio Should You Export: 16:9, 1:1, or 9:16?

Whichever matches your content and your audience's device. X's feed natively supports all three, so this is a creative call, not a platform restriction.

| Aspect ratio | Resolution to set in Resolve | Best for |
| --- | --- | --- |
| 16:9 landscape | 1920x1080 | Desktop viewing, screen recordings, repurposed YouTube content |
| 1:1 square | 1080x1080 | A middle ground that holds up in-feed on both mobile and desktop |
| 9:16 vertical | 1080x1920 | Mobile-first clips, the closest match to how most people scroll X on a phone |

**Vertical video and square video both play natively in X's feed, so the aspect ratio you export is a decision about your audience's screen, not a workaround for a platform limitation.** To set the frame in Resolve before you export, go to **File, Project Settings, Master Settings**, switch **Timeline resolution** to **Custom**, and enter the width and height for your chosen ratio. Do this before you edit, since reframing horizontal footage into a vertical crop afterward is a creative pass, not a checkbox.

If your export comes out with black bars down the sides instead of a clean crop, that's a project settings mismatch, not an X limitation, and our [guide to fixing black bars and wrong aspect ratios](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-black-bars-wrong-aspect-ratio-fix) covers the exact fix.

One edge case worth flagging: if you're delivering the same edit as both a 16:9 feed post and a 9:16 repost for Stories-style placements, don't crop the 16:9 master down to vertical as a last step. A straight center crop of a 1920x1080 frame to 1080x1920 throws away most of the width and keeps almost none of the composition your editor built. Reframe with Resolve's Smart Reframe tool or manually track the subject through the shot instead, so the vertical version is its own composition rather than a cropped leftover.

One more consideration for a 9:16 export specifically: X's own reply, like, repost, and share icons sit along the right edge and bottom strip of a vertical video in the app's feed view, the same kind of interface chrome that covers part of the frame on TikTok and Reels. Keep key text, logos, and any burned-in captions clear of the far right edge and the bottom of the frame in a vertical export. Resolve's Safe Area overlay, in the viewer's settings menu, gives you a title-safe guide you can toggle on while framing the shot, even though it was built for broadcast title-safety rather than social app chrome specifically. It's still the fastest way to check you haven't buried a caption under where X's UI will sit.

## What Frame Rate Should You Export for X, and What Happens If Your Timeline Doesn't Match Your Footage?

Whatever your timeline is already set to, in almost every case. X supports up to 60fps and recommends 30 or 60fps specifically, per [X Developer Platform's Media Best Practices](https://developer.x.com/en/docs/x-api/v1/media/upload-media/uploading-media/media-best-practices), but it doesn't reject other common rates, and converting your footage to a frame rate it wasn't shot at is more likely to introduce judder than to fix anything.

Here's how the common rates map to an X export:

| Your footage's native frame rate | Set your Resolve timeline and export to | Notes |
| --- | --- | --- |
| 23.976 or 24fps (cinematic look, most cameras' default) | 23.976 or 24fps | Falls outside X's "recommended" 30/60, but plays fine; don't force a 24-to-30fps conversion just to match the recommendation |
| 25fps (PAL regions, some broadcast work) | 25fps | Same logic as 24fps: X plays it, the recommendation just isn't tuned to PAL markets |
| 29.97 or 30fps (most vlogging and talking-head content) | 29.97 or 30fps | Matches X's recommended rate directly |
| 50fps (PAL high frame rate, some slow-motion masters) | 50fps for a PAL-region audience, or conform to 25fps for a standard-motion export | Not explicitly listed as recommended, but inside the 60fps ceiling |
| 59.94 or 60fps (sports, gaming, fast action, smooth motion content) | 59.94 or 60fps | Matches X's recommended rate directly, and it's the ceiling; nothing higher is supported |

**Converting a 24fps timeline to 30fps for an X export doesn't make the video smoother, it makes it juddery, since DaVinci Resolve has to invent frames that were never shot.** A straight frame rate conversion without optical flow or a similar interpolation method just duplicates frames unevenly, which reads as a subtle stutter on fast pans, the kind of artifact that's easy to miss in a quick preview and obvious the moment a viewer full-screens the post on a large phone. If your source footage and your project's frame rate already match, which they should if the project was set up correctly at the start, exporting at your timeline's native rate is always the right call for X, since nothing in X's spec rewards converting to 30 or 60fps if that's not where your footage started.

If you're mixing footage shot at different frame rates on one timeline, a common problem when combining a phone's 30fps clips with a camera's 24fps clips, the judder shows up before you ever reach the Deliver page, and it's worth fixing at the project level rather than trying to paper over it in the render. Our [guide to fixing a jittery mixed-frame-rate timeline](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-mixed-frame-rate-timeline-jittery) covers the project settings and per-clip conform options that actually solve it.

## What Bitrate Should You Restrict To for X?

Somewhere in X's own published 5,000-25,000 kbps range, matched to your resolution and how busy the footage is. X's ad platform gives the most specific anchor numbers it publishes anywhere: 6,000 kbps for 1080p, 5,000 kbps for 720p.

| Content type | Resolution | Bitrate to set in Resolve |
| --- | --- | --- |
| Talking head, static frame, slides | 720p | 5,000 kbps |
| Talking head, static frame, slides | 1080p | 6,000-8,000 kbps |
| B-roll, motion graphics, product demo | 1080p | 8,000-12,000 kbps |
| Handheld or fast-motion footage | 1080p | 12,000-16,000 kbps |
| Any of the above | 4K (Premium accounts only) | 20,000-25,000 kbps |

**X re-encodes every video you upload, so a bitrate far above its own recommended range buys you a slower upload, not a sharper post.** That's the same re-encode logic that governs YouTube and LinkedIn delivery, and it's worth remembering before you're tempted to max out the Quality dropdown on a 15-second clip. If your export comes out heavier than these numbers suggest it should, our [guide to fixing an oversized DaVinci Resolve export](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-export-file-size-too-large) covers the Quality-left-on-Automatic mistake that causes most of it.

A quick way to sanity-check a bitrate before you commit to a full render: multiply your target kbps by the duration in seconds, divide by 8 to convert bits to bytes, and you get an estimated file size in kilobytes. A 60-second 1080p export at 8,000 kbps lands around 60 MB, well inside any tier's limit; the same clip at 25,000 kbps lands around 188 MB, still fine for a non-Premium 512 MB cap but well past what the content needs. Run that math before rendering a long-form Premium upload, where the gap between "fits" and "doesn't" is a lot narrower.

## Should You Upload 4K to X?

Only if you're a Premium subscriber and you're uploading from the web or the iOS app, and even then, weigh it against how much heavier the file gets for a feed most people scroll on a phone.

X rolled 4K upload support out to select creators in April 2025, then expanded it to all Premium subscribers the following month, per [TechCrunch's report at the time](https://techcrunch.com/2025/04/30/x-is-rolling-out-support-for-4k-video-uploads) and [Social Media Today's coverage of the wider rollout](https://www.socialmediatoday.com/news/x-formerly-twitter-enables-4k-video-uploads/748314/). Non-Premium accounts don't get the option in the upload flow at all; the limit simply isn't there to hit.

Both of those reports, and X's own help documentation, name web and iOS as the supported upload paths. Neither names Android. That gap hasn't closed as of this writing, and X hasn't published a note explaining why. If you're on a Premium account uploading from an Android device, don't assume 4K support is there just because it is on iOS; render a short test clip first and check what resolution actually lands on the post, since an unsupported upload path is more likely to downscale silently than to throw an error.

In Resolve, targeting 4K for X means setting your timeline to 3840x2160, restricting Quality to somewhere in the 20,000-25,000 kbps range from the table above, and confirming your account has an active Premium or Premium+ subscription before you render. If any of those three conditions isn't met, the export still finishes, but the upload either gets downscaled on X's end or bounces off a limit that has nothing to do with your Deliver page settings.

Bit depth is a non-issue for this specific export, worth flagging since it comes up in other 4K delivery contexts: X's spec doesn't call for or accept anything beyond standard 8-bit color, so a free-version Resolve install, capped at 8-bit output, produces a file that's already exactly what X wants. There's no reason to reach for a 10-bit master or a Studio license just to hit X's 4K option specifically.

X's head of product, Nikita Bier, framed the platform's recent push on video tools plainly: "One of our biggest priorities is to give creators the tools to create original content & reward those creators," he said, discussing the video editor updates that shipped alongside the broader creator push, per [Social Media Today](https://www.socialmediatoday.com/news/x-formerly-twitter-updates-video-editor-green-screen-recording/824544/). The 4K upload option is part of that same push, not a separate, unrelated feature.

## Why Does X Autoplay Muted and Loop Short Clips, and What Does That Mean for Your Export?

Because that's the platform's default feed behavior, and it changes what a good export needs to include before you ever click render.

Video on X autoplays in the timeline with the sound off by default, and a viewer has to tap in to hear it. On top of that, a rule that's held since 2019 keeps short clips looping automatically: **a video under 60 seconds loops on X's feed, so a slow build in the first few seconds costs you replays a punchier cut would keep**, per [Digital Information World's coverage of the loop rule](https://www.digitalinformationworld.com/2019/02/under-60-seconds-twitter-videos-loop.html).

Two concrete choices follow from that, not just a philosophy. First, export subtitles as a separate SRT file rather than relying on X's automatic captions alone, since muted-by-default viewing means your on-screen text does the work sound normally would. Second, cut the first two or three seconds for someone with no audio and a video that's about to loop, not scroll past; a static title card that plays fine as an intro on YouTube can feel like dead air on a platform where the whole clip repeats every few seconds.

If you already built a subtitle track in Resolve, export it as SRT using the steps in the next section rather than burning captions into the picture, so the file stays editable if you catch a typo after the post is already live.

## How Do You Add Working Captions to a Video You Export for X?

Export the caption track as a standalone SRT file, then upload it separately from your video, not burned into the picture.

In Resolve's Deliver page, tick **Export Subtitle** in Render Settings and choose the option that writes a separate subtitle file rather than the burn-in option. Resolve writes an SRT alongside your video file with the same base filename. Open it in a plain text editor before you upload anything, just to confirm the timestamps and text landed the way you expect; a subtitle track built from auto-transcription in Resolve's Text-Based Editing tools can drift a frame or two if you trimmed the timeline after generating captions, and it's a thirty-second check that saves a re-upload.

On X's side, the caption workflow is narrower than you'd expect from a platform this size. **X accepts exactly one caption file per video, in SRT format only, uploaded as a separate step after the video itself finishes processing**, per [X's help center article on uploading a caption file](https://help.x.com/en/using-x/upload-caption-srt-file). There's no multi-language track selector on a standard post the way there is on YouTube; if you need captions in more than one language, you're posting the video more than once, or relying on X's own automatic captioning as a fallback for the languages you didn't cover with an SRT.

A few things that trip this workflow up:

- **Upload the video first, wait for it to finish processing, then attach the caption.** Attaching a caption file to a video that's still processing is a common cause of captions silently not appearing.
- **Save the SRT as UTF-8.** A file saved with a different text encoding can render as garbled characters or fail to attach at all, especially if your captions include accented characters or non-Latin text.
- **Keep the caption feature in mind as an account-level capability, not a universal one.** Community reports and X's own developer forum note the caption upload option has, at times, been gated to Media Studio or specific account types rather than available to every user by default; if you don't see an upload captions option under a posted video, that's the first thing to check, not your SRT file.
- **One file per video means one shot at getting it right.** If you catch a timing error after the video is live, re-export the SRT and re-upload it as a replacement rather than trying to edit captions in place; X doesn't offer an in-line caption editor for uploaded SRT files.

## How Do You Set a Custom Thumbnail for an X Video After You Post It?

Through X's own Media Studio, and it's a Premium feature, not something available to every account, so check your subscription before you go looking for a control that isn't there.

DaVinci Resolve doesn't export a separate thumbnail file for a video post the way it can for a podcast or a YouTube upload; the Deliver page renders your video, and that's the deliverable. X picks the first frame as the default thumbnail unless you override it after the video is live. In X's Media Studio, under the Library section, selecting a posted video surfaces a **Select thumbnail** option that lets you either pick a different frame from within the clip or upload a separate image file, per [X's Media Studio FAQ](https://help.x.com/en/using-x/media-studio-faqs). That uploaded image has to match your video's aspect ratio, so a 16:9 thumbnail for a 16:9 post, 9:16 for a vertical one, or X can crop or resize it in a way you didn't intend.

**If your X account doesn't have Premium, the thumbnail X shows is whichever frame the platform's own algorithm picks, not necessarily your best frame, and there's no workaround inside Resolve to force a specific one.** The practical fix for a non-Premium account is a compositional one: build a strong opening frame into the edit itself. Start the export on a frame with your subject centered, in focus, and free of a loading state or a black frame from a fade-in, since that first frame is what a non-Premium account is stuck showing as its thumbnail whether it flatters the video or not.

If you do have Premium and want a genuinely custom thumbnail rather than a frame pulled from the clip itself, export a single still frame from Resolve instead of the full timeline: on the Deliver page, set your In and Out points to a single frame, or use **File, Export, Still** on a frozen frame in the Edit page, save it as a JPEG or PNG at your export's exact resolution, and upload that file through Media Studio's thumbnail picker rather than relying on a frame from the rendered video.

## Should You Export a GIF Instead of a Video for X?

Sometimes, for a very specific kind of short, silent, looping clip, but a compressed H.264 video usually wins on quality and file size for anything with real motion.

DaVinci Resolve has exported animated GIFs natively since version 18.5: on the Deliver page, choose **Custom Export**, tick **Export Video**, set **Format** to GIF and **Codec** to Animated GIF, pick a resolution under 720p, and keep the frame rate modest. Our [full GIF export guide](https://tryuncle.com/learn/davinci-resolve/how-to-export-a-gif-from-davinci-resolve) covers the resolution and frame rate tradeoffs in more depth, since GIF file size scales with all three variables (resolution, frame rate, duration) at once, far more aggressively than a compressed video codec does.

On X's side, GIFs have their own limits that don't line up with the video table earlier in this guide: **animated GIFs are capped at 15 MB from the web and 5 MB from a mobile device**, per [X's help center article on posting pictures and GIFs](https://help.x.com/en/using-x/posting-gifs-and-pictures). If you export a 15 MB GIF on your desktop and someone reuses that same file from a scheduling app's mobile companion, it can bounce off the 5 MB ceiling that platform enforces on mobile uploads. Target 5 MB if the file needs to move reliably between devices, and treat 15 MB as the desktop-only ceiling, not a safe number to build around.

X also converts every GIF you upload into a silent MP4 for delivery, which is why a GIF on X autoplays and loops exactly like a video clip does, just without a sound toggle since there was never any audio to begin with. That conversion is also why a genuinely long or high-motion clip almost always looks better and weighs less as a proper H.264 export than as a GIF pushed through that same pipeline; GIF compression works frame by frame, without the motion prediction a video codec uses, so anything with more than a few seconds of real movement gets big fast. Reach for GIF format specifically when the clip is short, low-motion, and meant to loop seamlessly, a reaction clip or a UI demo rather than a highlight reel.

## Do Scheduling Tools and the X API Change Any of These Limits?

Yes, and this is the gap that catches people who've never hit it before: if you post through a third-party scheduler, Buffer, Hootsuite, Zapier, or a custom integration, rather than the X app itself, your Premium subscription's longer runtime and bigger file allowance may not travel with you.

X's chunked media upload API, the endpoint most scheduling tools use behind the scenes to post video on your behalf, documents its own video ceiling: **512 MB and 140 seconds per video**, per [X Developer Platform's chunked media upload documentation](https://developer.x.com/en/docs/x-api/v1/media/upload-media/uploading-media/chunked-media-upload) and its [media upload initialization reference](https://docs.x.com/x-api/media/initialize-media-upload). That's the same ceiling a non-Premium account hits natively, and nothing in the public API documentation carves out a separate, larger allowance tied to the posting account's Premium status the way the consumer apps do.

**A Premium subscription raises the limits you get inside X's own app; it does not automatically raise the limits a third-party API integration enforces on your behalf.** In practice, that means:

| Posting method | Practical video ceiling |
| --- | --- |
| X app or website, non-Premium account | 140 seconds, 512 MB |
| X app or website, Premium or Premium+ | Up to ~4 hours, up to 16 GB |
| Scheduling tool or custom integration using X's standard media upload API | 140 seconds, 512 MB, regardless of the account's subscription tier |

If a client's social team schedules everything through a third-party dashboard and asks why their Premium-length upload "didn't work," check the posting method before you re-render anything. The fix usually isn't a smaller export, it's posting that specific longer video natively from the X app instead of through the scheduler, at least until the integration you're using confirms it supports the higher limits. This shows up most often with tools like Buffer, Hootsuite, and Zapier-built posting flows, since they're built on X's public API rather than a special partnership with the platform. If a client's account runs everything through one of these, ask the tool directly whether it supports X's higher Premium limits before you build a longer master file around the assumption that it will. Some publish this in their own help docs; some don't mention it at all until an upload fails.

## Worked Example: One 4K Timeline, Four Different X Deliverables

Say you finished a 90-second product demo on a 3840x2160 timeline, and you need to post it four ways: as a normal feed post, as a 15-second paid ad, as a vertical repost for mobile-first viewers, and with a custom thumbnail so the launch post doesn't rely on whatever frame X picks on its own. Here's how the tables in this guide turn into four separate deliverables.

**Deliverable 1: the organic feed post.** Your account is Premium, so the full 90 seconds fits inside the roughly-2-hour, 8 GB ceiling with room to spare; the bottleneck here is quality, not the limit. In Render Settings, set Format to MP4, Codec to H.264, Resolution to your timeline's native 3840x2160 if you want to keep the 4K upload option (Premium, web or iOS only), or scale to 1920x1080 if you'd rather keep the file smaller and skip the 4K-specific caveats entirely. Set Quality to Restrict to and pick a bitrate from the B-roll and motion graphics row, 8,000-12,000 kbps at 1080p, or 20,000-25,000 kbps if you're staying at 4K. Audio: AAC, 48 kHz, stereo. Export subtitles as a separate SRT if the demo has voiceover, since it'll autoplay muted regardless of resolution. Before you export, check the Advanced Settings color space and gamma tags match your actual delivered color space rather than a leftover default.

**Deliverable 2: the 15-second ad cut.** This isn't a re-render of the same file with a shorter Out point; it's a distinct edit, since 90 seconds of product demo condensed to 15 seconds needs different pacing, not just a trim. Once that cut exists on its own timeline, export it against the in-feed video ad specs: MP4, H.264, 1920x1080 or 1280x720 depending on how much the ad platform's file size cap matters to you, Quality restricted to 6,000 kbps at 1080p or 5,000 kbps at 720p, and a final file size checked against the flat 1 GB ad ceiling regardless of your account's Premium status. At 15 seconds and 6,000 kbps, you're nowhere close to that limit; the constraint here is creative, not technical.

**Deliverable 3: the vertical repost.** Don't crop the 16:9 organic export down to 9:16 as a last step; you'll lose most of the frame's width and probably the product itself if it's not centered. Go back to the original 4K timeline, duplicate it, and either use Smart Reframe or manually keyframe a pan-and-scan crop that follows the product through the shot. Set the duplicated timeline's Custom resolution to 1080x1920, export MP4, H.264, Quality restricted to 8,000-12,000 kbps, same AAC audio settings as the first export. Because this version is meant for scrolling viewers on a phone, tighten the first two seconds specifically: no slow logo build, the product or the hook visible from frame one, since a video under 60 seconds loops on X's feed and a weak opening gets skipped, not rewatched. Keep the on-screen product name clear of the frame's right edge and bottom strip, since that's where X's feed icons sit on a vertical post.

**Deliverable 4: the thumbnail-ready still and a Media Studio pass.** Since this account has Premium, don't leave the thumbnail to chance on a product shot where the wrong frame could show an awkward mid-transition blur. Scrub the finished 90-second edit for the single frame that sells the product best, ideally one with the product fully in frame and any on-screen text settled rather than animating in. Export that frame as a still JPEG at your delivery resolution, either through a one-frame Deliver page render or a still export from the Edit page, and set it as the video's thumbnail through Media Studio once the main upload finishes processing. It costs nothing extra in render time, since you're not re-touching the video export at all, just handing X a better first impression than whatever frame it would have picked on its own.

Four exports, four render queue entries, and one thumbnail upload, roughly fifteen minutes of settings work once you know which row in which table applies to each one. Save each render as its own named preset, "X Feed 4K," "X Ad 15s," "X Vertical Repost," and the next product demo takes a fraction of the time this one did.

## What Are the Most Common X Export Mistakes?

Diagnose by symptom before you re-render blind.

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Upload rejected outright | File exceeds 512 MB (non-Premium) or 1 GB (any ad) | Check which limit applies, then restrict bitrate to fit |
| Video plays soft or blurry after posting | Bitrate too low for the resolution, or X still processing | Raise bitrate toward the top of the range for your content type; wait a minute and recheck |
| Upload accepted as a post but rejected from ads | File built to organic's Premium-tier size instead of the ad platform's flat 1 GB cap | Re-render with Quality restricted to a bitrate that lands under 1 GB for the duration |
| Colors look correct in Resolve but washed out or oversaturated on X | Color space or gamma tag mismatch between the timeline and the export | Set Advanced Settings' Color space tag and Gamma tag to match your actual delivered color, usually Rec.709 |
| Fast pans look stuttery after export | Timeline frame rate doesn't match source footage, or was converted without motion interpolation | Export at your footage's native frame rate instead of converting to 30 or 60fps |
| 4K option missing from the upload flow | Account isn't a Premium or Premium+ subscriber, uploading from an unsupported app, or on Android where 4K support isn't documented | Confirm subscription status; use web or iOS for 4K uploads |
| Captions never show a toggle | Subtitles burned into the picture instead of exported as SRT, or the caption attached before the video finished processing | Re-export as a separate SRT file; wait for the video to finish processing before attaching captions |
| Thumbnail shows an awkward or blurry frame | Non-Premium account, or a Premium account that never set a custom thumbnail in Media Studio | Build a strong first frame into the edit, or set a custom thumbnail through Media Studio if you have Premium |
| GIF fails to attach or looks compressed | File exceeds 15 MB (web) or 5 MB (mobile), or resolution/frame rate too high for GIF compression | Drop resolution under 720p and frame rate to 10-15fps; target 5 MB if the file needs to move between devices |
| Carousel or Website Card ad rejected | Cards don't share one aspect ratio, or resolution doesn't match the 1:1 or 1.91:1 spec for that card type | Reframe every card to the same aspect ratio before exporting |
| Premium-length video fails through a scheduling tool | Third-party API integration enforces the standard 512 MB / 140 sec ceiling regardless of your account's Premium tier | Post that specific video natively through the X app, or confirm your scheduler's documented limits |
| 4K export takes far longer to render than expected | Free version encoding H.264/H.265 in software instead of Studio's hardware-accelerated path on Windows or Linux | Render at 1080p if speed matters more than a 4K option most viewers can't use anyway, or accept the longer render on Free |
| Silent audio or the wrong mix | Wrong output track selected in the Audio tab, or codec not set to AAC | Confirm the main mix bus is selected and audio codec is AAC |
| Vertical video shows black bars on the sides | Exported in a 16:9 frame instead of a vertical Custom resolution | Set Project Settings, Master Settings to a Custom 1080x1920 resolution before re-exporting |
| Format rejected outright | Exported as an unsupported wrapper instead of MP4 or MOV | Re-export as MP4 with H.264 video and AAC audio |

## Quick Reference: Every X Export Number in One Table

Everything above, condensed into a single lookup, organized by what you're actually building.

| You're exporting... | Container/codec | Resolution | Bitrate | Max duration | Max file size |
| --- | --- | --- | --- | --- | --- |
| Standard post, non-Premium | MP4, H.264, AAC | 1920x1080 / 1080x1080 / 1080x1920 | 5,000-16,000 kbps | 140 sec | 512 MB |
| Standard post, Premium/Premium+ | MP4, H.264, AAC | Up to 3840x2160 (web/iOS) | 8,000-25,000 kbps | Up to ~4 hrs | 8-16 GB |
| In-feed video ad | MP4, H.264, AAC | 1920x1080 max, 1280x720 recommended | 5,000-6,000 kbps | 15 sec recommended | 1 GB |
| Video Website Card ad | MP4, H.264, AAC | 1200x1200 | 5,000-6,000 kbps | 15 sec recommended | 1 GB |
| Amplify Pre-roll ad | MP4, H.264, AAC | 1200x1200 recommended | 5,000-6,000 kbps | 6-15 sec | 1 GB |
| Animated GIF | GIF, Animated | Under 720p | N/A | Short, looping | 15 MB (web) / 5 MB (mobile) |
| Through a third-party scheduler | MP4, H.264, AAC | Same as non-Premium row | Same as non-Premium row | 140 sec | 512 MB, regardless of tier |

Bookmark this table. Everything else in this guide explains why these numbers are what they are and how to hit them from Resolve's Deliver page; this is what you actually want open in a second tab while you're setting Render Settings.

## Is There an AI Tool That Can Help You Find These Settings Faster?

TryUncle is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words and Uncle points at the exact control on your screen, live, inside the project you're already working in, whether that's the Quality dropdown, the Custom resolution field, or the audio sample rate setting this guide covers above.

That question, someone knowing a setting needs to change for a specific platform and not being able to find where Resolve put it, is one of the recurring questions in our 100,000+ member DaVinci Resolve editing community. After seven years of professional, commercial video editing across client platforms and delivery specs, that's the exact gap we built TryUncle to close.

It's worth being straightforward about where TryUncle fits next to the other AI tools built around DaVinci Resolve, since the category has gotten crowded and the jobs involved are genuinely different.

| Tool | What it does | Touches your timeline? | Helps with an X export by... |
| --- | --- | --- | --- |
| [CutAgent](https://www.cutagent.ai/) | Executes cuts from a typed instruction | Yes | Automating assembly, not delivery specs |
| [Sottocut](https://sottocut.com) | Proposes edits, captions, and reordering for review | Yes | Building the caption track, not export settings |
| [PremiereCopilot](https://www.premierecopilot.com/pricing) | Automates specific editing tasks | Yes | Reducing hands-on trim time, not export size |
| [Eddie AI](https://www.heyeddie.ai/workflows/davinci-resolve) | Answers questions in a chat window | No | Explaining concepts, not showing where the control lives |
| TryUncle | Watches your screen and points at controls | No | Finding the resolution, bitrate, or subtitle setting live, on your own screen |

**Guided practice inside Resolve beats hunting through menus on a deadline, because a spec table tells you what to check while a pointed assistant shows you exactly where it lives on your specific screen.** That's a meaningfully different job than any tool that edits for you, and it's also different from the worked example a few sections up: the tables and the walkthrough tell you what settings to use, while something like Uncle helps when you know the number but can't find the field it goes in.

TryUncle is a paid subscription, currently $29.99/month in founder pricing for the first 100 seats, cancel anytime, macOS only; check [TryUncle](https://tryuncle.com/?utm_source=learn&utm_medium=blog&utm_campaign=davinci-resolve-export-settings-for-twitter-x) directly for the current rate. It won't render your export for you, and it isn't a substitute for the tables in this guide. If you're mid-export right now and can't remember which field restricts bitrate, Uncle can point at it on your own Deliver page while you set it.

## The Short Version

Export MP4, H.264, AAC audio at 44.1 or 48 kHz, matched to your timeline's native resolution and native frame rate: 1920x1080 for 16:9, 1080x1080 for square, or 1080x1920 for vertical, at whatever fps your footage was actually shot at. Restrict the bitrate to somewhere between 5,000 and 25,000 kbps depending on resolution and motion, tag your color space and gamma correctly so the export doesn't wash out on upload, and leave the keyframe interval on Resolve's default unless you're troubleshooting a specific playback problem. Check which duration and file size limit applies to you before you render: 140 seconds and 512 MB on a free account, hours-long runtimes and up to 16 GB on Premium or Premium+, or a flat 1 GB no matter what if the file is headed to an ad campaign, and remember that a third-party scheduling tool posting through X's standard API may hold you to that same 512 MB, 140-second ceiling regardless of your subscription. Export captions as a separate SRT file rather than burning them in, since X plays every video muted by default, loops anything under 60 seconds, and accepts exactly one caption file per post. If you're on a Premium account, set a real thumbnail through Media Studio instead of leaving it to whichever frame X picks.

**Twitter's rebrand changed the platform's name, its Premium tiers, and its file size ceilings, but it never changed what DaVinci Resolve needs to hand it: a clean H.264 MP4 at the right resolution, frame rate, and color tag for your account.** Match the row in this guide's tables to your account and your content, save the settings as a preset, and the rest of your export list takes care of itself.

If you're delivering the same timeline to more than one platform, our [DaVinci Resolve export settings for YouTube](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-export-settings-youtube) guide and our [LinkedIn export settings guide](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-export-settings-for-linkedin-video) cover the codec and bitrate walkthroughs for those destinations from the same Deliver page.

## FAQ

### What is the best export format for Twitter (X) in DaVinci Resolve?

MP4 with the H.264 video codec and AAC audio. It's the combination named first in both of X's own spec pages, for regular posts and for video ads, and it's what DaVinci Resolve's built-in Twitter preset and its H.264 Master preset both produce by default.

### What is the maximum video length for Twitter (X)?

140 seconds, or 2 minutes 20 seconds, if you're not an X Premium subscriber. Premium and Premium+ subscribers can upload videos under about 2 hours at 1080p, or up to roughly 4 hours at 720p, per X's help center.

### What is the maximum file size for a video on Twitter (X)?

512 MB for a non-Premium account. X Premium subscribers get up to 8 GB for videos under about 2 hours, and up to 16 GB for longer uploads capped at 720p. Video ads through X's ad platform are capped at 1 GB regardless of subscription tier.

### Does DaVinci Resolve have a built-in preset for Twitter (X)?

Yes, under its original name. Resolve's Deliver page and Quick Export both still list a preset called Twitter, not X, alongside YouTube, Vimeo, TikTok, and Dropbox. It's a reasonable starting point, but check its resolution and bitrate against the tables in this guide rather than trusting the label alone.

### What resolution should I export for Twitter (X)?

Match your timeline: 1920x1080 for 16:9 landscape, 1080x1080 for a square post, or 1080x1920 for 9:16 vertical. X's own developer documentation lists 1280x720, 720x1280, and 720x720 as baseline recommended sizes, but a 1080p export plays back at full quality for anyone viewing with X Premium.

### Can I upload 4K video to Twitter (X)?

Yes, if you're an X Premium subscriber uploading from the web or the iOS app. X expanded 4K upload support to all Premium subscribers in May 2025, after testing it with select creators the month before. Non-Premium accounts don't get the option at all.

### What's different between X's video ad specs and its regular post specs?

The file size ceiling drops from 512 MB, or a Premium subscriber's multi-gigabyte allowance, to a flat 1 GB cap for every ad, regardless of who's running the campaign. Ads also recommend a much shorter runtime, 15 seconds or less, against the 140-second organic limit, and Amplify Pre-roll ads add their own 1:1 aspect ratio recommendation on top.

### Is there an app that helps you while you're actually using DaVinci Resolve to find these settings?

Yes. TryUncle is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words and Uncle points at the exact control on your screen, live, inside your own project, whether that's the Quality dropdown, the Custom resolution field, or the audio sample rate setting this guide covers above. It's a paid subscription, currently $29.99/month in founder pricing for the first 100 seats.

## Sources

- [X Help Center: How to share and watch videos on X](https://help.x.com/en/using-x/x-videos)
- [X Help Center: About longer videos for X Premium subscribers](https://help.x.com/en/using-x/premium-longer-videos)
- [X Help Center: About X Premium](https://help.x.com/en/using-x/x-premium)
- [X Help Center: How to post pictures or GIFs](https://help.x.com/en/using-x/posting-gifs-and-pictures)
- [X Help Center: How to upload a caption (.srt) file to Posts](https://help.x.com/en/using-x/upload-caption-srt-file)
- [X Help Center: Media Studio FAQs](https://help.x.com/en/using-x/media-studio-faqs)
- [X Business: Creative ad specifications](https://business.x.com/en/help/campaign-setup/creative-ad-specifications)
- [X Developer Platform: Media Best Practices](https://developer.x.com/en/docs/x-api/v1/media/upload-media/uploading-media/media-best-practices)
- [X Developer Platform: Chunked media upload](https://developer.x.com/en/docs/x-api/v1/media/upload-media/uploading-media/chunked-media-upload)
- [X Developer Platform: Initialize media upload](https://docs.x.com/x-api/media/initialize-media-upload)
- [Social Media Today: X rolls out updated video editor, including green screen recording](https://www.socialmediatoday.com/news/x-formerly-twitter-updates-video-editor-green-screen-recording/824544/)
- [Social Media Today: X Rolls Out Support for 4K Video Uploads](https://www.socialmediatoday.com/news/x-formerly-twitter-enables-4k-video-uploads/748314/)
- [TechCrunch: X is rolling out support for 4K video uploads](https://techcrunch.com/2025/04/30/x-is-rolling-out-support-for-4k-video-uploads)
- [Sprout Social: Always up-to-date guide to social media video specs](https://sproutsocial.com/insights/social-media-video-specs-guide/)
- [Digital Information World: Twitter videos are now on 'automatic loop' mode](https://www.digitalinformationworld.com/2019/02/under-60-seconds-twitter-videos-loop.html)
- [DoChipo: X/Twitter Ad Size, A Complete Guide for all X/Twitter Ad Formats](https://www.dochipo.com/twitter-ad-size/)
- [Tweetfull: Complete Guide to X Amplify Pre-Roll Ads](https://tweetfull.com/blog/twitter-pre-roll-specs-complete-guide-to-x-amplify-pre-roll-ads/)
- [Haivision: Video Encoding Best Practices, 6 Practical Tips for Optimizing Latency, Bandwidth, and Picture Quality](https://www.haivision.com/blog/all/video-encoding-best-practices-6-practical-tips-for-optimizing-latency-bandwidth-and-picture-quality/)
- [DaVinci Resolve Reference Manual: Using Presets for Fast Rendering (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part3929.htm)
- [Blackmagic Design: DaVinci Resolve vs DaVinci Resolve Studio comparison](https://www.blackmagicdesign.com/products/davinciresolve/compare)
- [DaVinci Resolve - Studio (Blackmagic Design)](https://www.blackmagicdesign.com/products/davinciresolve/studio)
- [DaVinci Resolve product page (Blackmagic Design)](https://www.blackmagicdesign.com/products/davinciresolve)
- [CutAgent (product site: features, pricing, FAQ)](https://www.cutagent.ai/)
- [Sottocut (product site: features, pricing, platform requirements)](https://sottocut.com)
- [PremiereCopilot pricing](https://www.premierecopilot.com/pricing)
- [Eddie AI for DaVinci Resolve (native integration workflow page)](https://www.heyeddie.ai/workflows/davinci-resolve)
- [TryUncle](https://tryuncle.com)
- [TryUncle FAQ](https://tryuncle.com/faq)