Rendering Export Settings for Instagram, Reels and AI Video

A rendering that looks sharp on your studio monitor can come out soft, cropped strangely, or off in color once it lands on Instagram, in a Reel, or inside an AI video tool. The usual cause isn't the render itself — it's the export dialog: pixel dimensions, aspect ratio, color profile and file format, chosen before you hit save. This guide covers current Instagram and Reels sizes, why a downsized export often looks softer than the source, and where the custom-resolution field lives in Enscape, V-Ray and other renderers, so rendering export settings stop being a guess.

Key takeaways

• Posting in the Instagram app allows 1.91:1 to 3:4 (1080 pixels wide, 566–1440 tall); posting through Meta's publishing API instead narrows that to 4:5–1.91:1, capped at 1440 pixels wide.
• Common export sizes: 1080×1350 (4:5) for the feed, 1080×1440 (3:4) for the taller profile grid, and 1080×1920 (9:16) for a Reel.
• Cropping a 16:9 render down to 9:16 keeps only about a third of the width, so render wide at 4K or higher, or save a separate vertical camera view instead.
• Keep a full-resolution export as your master file, then downsize and sharpen it yourself for Instagram rather than relying on the app's own resize.
• Enscape and V-Ray both have a documented custom-resolution field; other renderers have one too, though the exact menu differs by tool and version.

Instagram and Reels sizes at a glance

The same rendering often serves more than one purpose. A hillside house exterior might end up on the Instagram feed, in a Reel, inside an AI video tool, and on the studio's own website, and each of those expects a different frame.

As of September 2026, Instagram's help center puts the app's own feed range at 1.91:1 to 3:4 — a width of 1080 pixels with a height between 566 and 1440 — and crops anything outside that range automatically. Posting instead through Meta's publishing API narrows that range to 4:5–1.91:1 and caps width at 1440 pixels; taller files get scaled down and narrower ones scaled up to fit. Reels and Stories fill the screen edge to edge at 9:16.

For a practical export size: 1080×1350 (4:5) is the common feed choice, 1080×1440 (3:4) now fills the taller profile-grid tile Instagram rolled out in 2025, and 1080×1920 (9:16) fills a Reel. If the same rendering is also headed into an AI video tool, the aspect-ratio math above doesn't apply the same way: Arch2Video accepts exactly six images from one project and its AI director builds its own cinematic 9:16 reference frame for each scene, interpreting the source image rather than cropping it. That interpretation can change small details, so plan on reviewing the finished film before you post it.

Decide the export size up front rather than resizing later, so a crop doesn't cut off a chimney or a corner detail after the fact. If a rendering is being prepared for a short film specifically, see preparing renderings for video for how that file-prep step fits the rest of the workflow.

Resolution: why a rendering can look soft after export

Hootsuite's guide to social media image sizes recommends exporting Instagram feed images around 1080 pixels wide — 1080×1350 for a 4:5 post, 1080×1920 for a Reel — while Meta's own publishing spec scales anything wider than 1440 pixels down on upload. In practice, there's little reason to export a feed image much past 1440 pixels wide for a file that's going straight to Instagram and nowhere else.

A rendering that looks blurry on Instagram is rarely a resolution problem by itself. Two more common causes: a JPG exported at a low quality setting, which bakes in compression artifacts before the file leaves your computer, and letting Instagram's own upload compression do the only resizing on top of whatever your renderer or editor already did. Export a delivery copy close to the size the destination needs, at a high JPG quality setting with a touch of output sharpening, rather than handing over a much larger file and trusting an automatic resize to keep it sharp.

An AI video tool is a different case, since the file isn't headed to a phone screen first. Keep the highest-resolution export you have on file: Arch2Video accepts full-resolution camera files — JPG, PNG or WebP — and downscales them automatically, so there's no benefit handing it a copy already resized for Instagram. Export once at your renderer's native resolution, keep that as the master, and downscale a copy for each destination afterward; export only a 1080-pixel version and you'll need a re-render, not a resize, the day a different use calls for more.

Color space, bit depth and file format

Meta's Instagram media specification states that published images must use the sRGB color space, and that anything in a different color space gets converted to sRGB automatically rather than rejected. That makes sRGB the safe default for a delivery copy headed anywhere, not just Instagram.

Chaos's documentation for Enscape's output settings and V-Ray's render output settings shows no separate color-profile choice in the export panel — both render straight to sRGB by default. If you finish a render in an image editor from a wider-gamut or EXR master, look for a color-profile or "convert to" option when saving the delivery JPG, and choose sRGB there.

Bit depth matters less than color space here: export the delivery JPG or PNG as 8-bit even if your working file carries more, since a phone screen doesn't need the extra precision (PNG itself can store more than 8 bits per channel, so this is a save-time choice, not a fixed property of the format).

On format: JPEG is the only format Meta's publishing API accepts, capped at 8 MB, making it the safest default for a rendering headed to Instagram through a scheduling tool or an uncertain path. Render engines typically export JPG or PNG for delivery, plus EXR or TGA for further post-production; both JPG and PNG work for the AI-video workflow above too. PNG is worth the larger file for crisp architectural linework, since JPG compression can introduce artifacts along hard edges — though for a straightforward Instagram post, a high-quality JPG is usually enough, since the platform re-encodes every image it receives regardless of format.

Custom resolution in Enscape, V-Ray and other renderers

Every mainstream renderer lets you set a custom output width and height, but the field sits in a different place in each one, often behind an aspect-ratio lock. Two vendors document the exact steps below; for the rest, the setting exists, but confirm the current wording in your installed version.

Enscape's steps and V-Ray's aspect-ratio lock come from Chaos's Enscape documentation and V-Ray render output documentation, current as of September 2026. Lumion, D5 Render and Twinmotion all support a custom width and height too, but menu names shift between releases, so treat those rows as a starting point rather than a screenshot from an old version.

Composing for a vertical crop

If you render wide and plan to crop into 4:5 or 9:16 later, the math matters more than it looks. Cropping a 16:9 frame down to 9:16 while keeping the full height leaves only about a third of the original width — a 1920×1080 render crops down to roughly 608×1080, well short of a Reel's 1080×1920. A true 1080×1920 crop from a 16:9 original needs a source at least about 3,413 pixels wide. Render at 4K or higher for this route, or save a separate vertical camera view and render it directly at 9:16 instead, which sidesteps the math altogether.

Composition in the original render still decides how well a crop works. Keep the focal detail centered, or at least well inside the frame, with clear margin on both left and right edges; a wide shot with the building pushed into one corner loses that corner the moment it's cropped tall. A courtyard garden framed dead-center with even margin on both sides holds up far better under a tight crop than an asymmetrical composition does.

If the same wide file is headed into an AI video tool instead of a crop, that math doesn't apply: choosing and checking the six images for an architecture video covers how a wide original gets recomposed into a vertical scene there, and what that recomposition can still miss near an edge.

Reels carry a separate composition concern once Instagram's own interface — captions, the profile icon, action buttons — sits on top of the video. That's specific to Reels rather than a rendering export setting; see Reels for architecture firms for the safe-area percentages worth keeping clear.

A pre-export checklist

Before you hit export, confirm:

• Aspect ratio matches the destination: 4:5 or 3:4 for a feed post, 9:16 for a Reel, or a wide original if the same file needs to serve more than one destination.
• Resolution matches the destination: roughly 1080 to 1440 pixels wide for Instagram, or your renderer's full-resolution export if the same file is also going into an AI video tool.
• Color space is sRGB; convert explicitly if you graded the delivery copy from a wider-gamut or EXR master.
• File format is JPG for a scheduling tool or Meta's publishing API — the safest single choice if a file might travel either path; an AI video tool can also take PNG or WebP directly.
• The subject sits centered with margin on both sides, in case the file gets cropped to a different aspect ratio later.
• No watermark, logo or on-screen text baked in — add a studio logo after upload instead; baked-in text can look distorted once an image is turned into motion.

Frequently asked questions

What aspect ratio should I render at for Instagram?

It depends on how the file gets posted. Directly through the Instagram app, the feed accepts 1.91:1 to 3:4 — 1080 pixels wide, 566 to 1440 tall. Through Meta's publishing API or a scheduling tool, the range narrows to 4:5–1.91:1, capped at 1440 pixels wide. If you're not sure which path a file will travel, 4:5 (1080×1350) satisfies both.

What resolution should I export renderings at?

Straight to Instagram, 1080 pixels wide meets the app's own recommended size, and Meta's publishing API accepts up to 1440 wide before scaling anything larger down. For an AI video tool, export at your renderer's full resolution instead: a full-resolution master gives you one file to downscale for every destination, rather than several renders at different sizes.

Does Instagram accept PNG renderings, or only JPG?

Meta's publishing API accepts JPEG only, with an 8 MB limit, so JPG is the safest default when you're posting through a scheduling tool or not certain which path a file will take. PNG still has a place for a master file or an AI-video upload, where lossless compression protects crisp linework.

Why does my rendering look blurry on Instagram?

Usually it's compounding compression, not resolution alone: a JPG exported at a low quality setting gets resized again by Instagram's own upload process, losing sharpness twice. Export a delivery copy close to the size you need — 1080 to 1440 pixels wide for the feed — at a high JPG quality setting with a touch of output sharpening, rather than handing over a larger file and letting the automatic resize do the work.