Instagram Reels Export Settings in DaVinci Resolve

Short answer: for a normal SDR Instagram Reel, edit in a 1080 × 1920 vertical timeline, reframe every shot, then export a Single Clip as MP4 with H.264 video and AAC stereo audio. Work at 30 fps or higher, the Reels minimum in Instagram's Help Center, use progressive scan and keep the color pipeline consistent with Rec.709. When Resolve offers a bitrate limit, 10,000–16,000 Kb/s is a practical starting range for 1080 × 1920 footage. Instagram doesn't ask for that number; it's simply a clean source quality to start from.

The Deliver page can't rescue a landscape edit that was never recomposed for a phone. I treat a Reel as its own vertical delivery: duplicate the timeline, fix the framing, check titles against the phone interface, then hand Instagram a clean source file to encode.

Instagram Reels export settings: the practical preset

Meta's official Instagram Reels Publishing API sample lists MOV or MP4 containers, H.264 or HEVC video, AAC audio, progressive scan and 23–60 fps, caps video at 25 Mbps VBR, and recommends 9:16 to avoid cropping or blank space. Those specs cover media sent through the Publishing API. For uploads in the app, Instagram's Help Center gives a shorter list: a 1.91:1 or 9:16 aspect ratio, at least 30 fps and at least 720 pixels. MP4 with H.264 video, AAC audio and a 1080 × 1920 frame fits both, which makes it the safest default Resolve profile.

1. Make a separate 1080 × 1920 timeline

If the main edit is landscape, duplicate its timeline before you change anything. Open the copy's timeline settings, turn on custom settings and set the resolution to 1080 × 1920. Builds that show Use vertical resolution swap the width and height for you, but check the result before you trust it. A duplicate also keeps the original frame rate. If a 24 or 25 fps edit needs a 30 fps Reel, create a new timeline instead, uncheck Use Project Settings, choose 30 fps there, then copy the edit across and check the motion.

Leave the original timeline alone. A landscape master and a vertical Reel need different compositions, and serving both from one canvas makes every later revision harder.

The aspect-ratio guide explains how timeline size, output size and clip reframing differ. For Reels, that difference is the foundation of the export. Skip it and no render setting will fix the result.

2. Reframe every shot for the portrait canvas

Changing the canvas doesn't compose the shot. Depending on the project's image-scaling settings, Resolve may center-crop, scale or leave empty space, but it can't decide which face, product or gesture matters.

Go through the duplicated timeline cut by cut. Use Inspector Zoom and Position to keep the intended subject in frame, and watch for motion entering from the cropped sides. Check compound clips, Fusion compositions, adjustment clips, subtitles and lower thirds on their own, because their transforms can react differently to the new canvas.

Don't stretch a landscape clip to fill 9:16. Keep its proportions, crop on purpose, and accept that some shots will need a new keyframed pan or a different source angle. A vertical version is a new edit, not a rotated export.

3. Configure Custom Export on the Deliver page

Open Deliver and choose Custom Export. Select Single Clip unless you have a real reason to render each timeline clip separately. Set Format to MP4 and Codec to H.264 if your system offers them. Resolve's manual documents a TikTok preset with the same basics, including a Use Vertical Resolution box, but no Instagram preset, so Custom Export keeps every choice in front of you.

Set the resolution to 1080 × 1920. When Match Timeline Settings is on in the Output Scaling part of the Image Scaling settings, Deliver picks up the timeline resolution by default, so you're mostly confirming it. Check that the scan is progressive. For a single-clip render, Frame rate defaults to the timeline rate, and the manual describes the other choices as variations of that rate, such as 23.98 or 24, which change file metadata. That's why the frame-rate decision belongs on the timeline. Encoder names and some advanced controls vary by operating system, Resolve edition and hardware, so use the matching controls your installation shows.

If the Render Queue, export range or audio controls are new to you, the full DaVinci Resolve export walkthrough covers them. This guide sticks to the decisions that change a Reel.

4. Treat bitrate as a starting point, not a platform law

Instagram will encode the upload again. No Resolve setting forces the platform to keep every source bit, and a giant file won't bypass that processing.

If the selected encoder offers an automatic or quality-based mode, a clean high-quality export is a fine starting point. If you prefer Restrict to, I'd begin around 10,000–16,000 Kb/s for a 1080 × 1920 H.264 Reel and inspect a short local export. That sits well under the 25 Mbps VBR ceiling in Meta's API sample. Fast movement, fine textures, confetti, water and added grain can need more room than a talking-head shot against a clean background.

Treat that range as editorial guidance. Meta doesn't list it as an upload requirement. What matters is whether the local file keeps the detail you care about before Instagram touches it. If you also need a smaller review or transfer copy, the Resolve file-size guide shows how to cut size without changing several variables at once.

5. Export AAC audio and check the actual output path

Open the Audio section in Render Settings and turn on Export Audio. Choose AAC, stereo and 48 kHz when they're available. A bitrate between 192 and 320 Kb/s makes a sensible working range for a normal Reel. Meta's API sample lists 128 kbps audio for API uploads, so the higher range just hands the encoder a cleaner source. Instagram doesn't treat it as a pass/fail line.

Watch Resolve's main output meter before rendering, then open the finished file outside Resolve. A timeline can sound fine while you edit and still render the wrong bus, or no audio at all, if the output source is set up wrong. Check the start and end, dialogue level, music balance and whether stereo plays as expected on a phone.

6. Keep the SDR color pipeline consistent

For a standard SDR Reel, keep the project, timeline, monitoring choices and delivery tags in line with a normal Rec.709 workflow. An output metadata tag isn't a conversion. If the project was graded in another color space, use the intended color-management or output-transform path. Changing tags at the final export won't do that job.

Check the local file in a color-managed player and on a second device before you blame Instagram. If the local file already looks washed out, too dark or oversaturated, fix the pipeline before uploading.

7. Keep titles, faces and logos away from interface overlays

A 9:16 frame can still fail as a Reel when the caption line, profile controls or action buttons cover important content. Overlay positions change with app revisions and viewing context, so I don't rely on one permanent pixel diagram.

Keep important text and logos away from the extreme top, bottom and right edges, and give subtitles enough room above the lower interface. If exact placement matters, make a private test upload and look at it on the devices your audience actually uses. Resolve's clean Viewer can't predict every live overlay.

8. Check the local file before uploading

Render a short representative section first. Open it outside Resolve and confirm:

• the file is 1080 × 1920 and displays vertically without black side bars;
• faces and products sit where you framed them, with nothing blindly centered;
• text reads at phone size and stays clear of the edges;
• motion, gradients and fine detail survive the local encode;
• audio is there, balanced and coming from the intended output;
• the picture has the expected SDR color and contrast.

In Instagram, turn on Upload at highest quality. Instagram's Help Center puts it under your profile: Menu, then Your app and media, then Media quality. The path can move between app versions, so search Settings for “media quality” if it isn't there. Upload on a stable connection and give the platform time to finish processing before you judge the result.

Why a Reel still looks soft or wrong after export

The local file is already soft

Check that the export really is 1080 × 1920, the source has enough detail for the crop, and scaling hasn't blown a small part of a landscape frame up too far. Look at the local file at its actual display size. More bitrate can't restore detail that the crop or source never had.

The local file is sharp but Instagram looks soft

Turn on the highest-quality upload option, use a stable connection, wait for processing, and compare the same Reel after the app has built its playback versions. Don't change codec, frame rate, bitrate and color settings all at once. Change one variable and make another short upload.

The Reel has black bars or the image is stretched

Go back to the vertical timeline. Black bars usually mean the clip or the output didn't fill the portrait canvas. Stretching means the original proportions changed. Reframe with crop, scale and position, and keep the source aspect ratio.

Titles are hidden by buttons or captions

Move critical graphics inward and upward, then test against the current Reels interface. One old safe-zone template won't stay exact forever, so don't lean on it alone.

The colors change after upload

Check the local export first. Confirm the project's color-management and output-transform choices, then keep delivery tags consistent with the intended SDR file. Metadata alone can't repair a wrong transform.

My final Reels export check

Before a file leaves Resolve, I want it to pass three checks: the vertical edit looks intentional, the local H.264/AAC export is clean, and the important content survives a phone interface. Get those three right and Instagram receives a strong source. If one is wrong, a more aggressive bitrate only makes the wrong file bigger.

For another destination, start from the DaVinci Resolve export settings hub. This Reels recipe doesn't carry over to YouTube, transparency, audio-only or client-master delivery.

Instagram Reels export FAQ

Should I export Instagram Reels at 30 fps?

Yes, 30 fps or higher is the safe choice, because Instagram's Help Center lists 30 fps as the minimum frame rate for Reels. Meta's Publishing API sample accepts 23–60 fps, but that applies to API uploads. If the edit already runs at 30 or 60 fps, keep it. Converting 24 or 25 fps material to 30 fps is a motion decision that can add duplicated or blended frames. Resolve's render Frame rate follows the timeline, so set 30 fps when you create the vertical timeline and check the motion before you upload.

Is 1080 × 1920 the best Resolve resolution for a Reel?

It's the practical default for a Full HD 9:16 Reel, and it clears the 720-pixel minimum in Instagram's Help Center with room to spare. The key is to build or duplicate a vertical timeline, reframe the shots there, then make the output match that timeline.

What bitrate should I use for a 1080 × 1920 Reel?

For H.264, 10,000–16,000 Kb/s is a useful starting range when Resolve offers a bitrate limit. Treat it as an editorial starting point, inspect a short local export, and give complex motion or texture more room when it needs it. Meta doesn't require that range; its API sample only sets a 25 Mbps VBR ceiling.

Does Instagram support H.265 from DaVinci Resolve?

Meta's Reels Publishing API documentation lists H.264 and HEVC for API-published media. That doesn't guarantee every app-upload workflow or device handles an H.265 file the same way. When compatibility matters, MP4 with H.264 is still the simpler default for a normal Resolve export.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.