# Instagram Reel Size: A 9:16 Canvas and an Export QA Checklist > Use a 9:16 working canvas for Instagram Reels, distinguish Meta's API specifications from app behavior, and review the final video with a practical export checklist. - Canonical: https://fluxgravity.io/guides/instagram-reel-size - Published: 2026-10-11 - Content type: guide Start with a 9:16 vertical composition, then inspect the exported file and its actual preview. Pixel dimensions alone cannot tell you whether the Reel is readable or ready to publish. ![Original diagram showing a 9:16 Reel working canvas beside export and preview checks](https://fluxgravity.io/images/editorial/instagram-reel-size-review.svg) *Original FluxGravity diagram. The 9:16 frame is drawn to proportion; the inner review area is illustrative, not a Meta-defined pixel safe zone.* ## What size should an Instagram Reel be? **Answer:** Use a 9:16 vertical working canvas. A 1080 x 1920 pixel export is one practical example of that ratio, not a universal requirement for every Instagram upload path. Meta's Instagram Reels Publishing API sample recommends a 9:16 aspect ratio to avoid cropping or blank space. Meta's Reels advertising guidance also encourages 9:16 video with important content kept clear of interface areas. Those are useful production references, but an API specification and an advertising recommendation do not establish every rule in the consumer Instagram app. Treat the app's current upload warning and final preview as the deciding checks for your account and placement. The number pair 1080 x 1920 means 1080 pixels wide and 1920 pixels high. Dividing both by 120 gives 9 x 16. A 720 x 1280 file has the same shape but fewer pixels; a 1080 x 1350 file has a different 4:5 shape. If someone asks for the Reel size, confirm whether they mean frame shape, export resolution, file format, file size, or the visible crop. A single number cannot answer all five questions. This guide covers an organic Reel preparation workflow and calls out when evidence comes from Meta's API or ads material. It does not claim a Reel was uploaded from a live account during this review. Interface controls, acceptance rules, and display surfaces can change. Keep the approved source video and use the preview in the publishing surface you actually plan to use. - Working shape: 9:16 portrait. - Example canvas: 1080 x 1920 pixels. - Final check: the current destination preview and any upload warnings. ## Keep aspect ratio and resolution separate **Answer:** Aspect ratio describes the frame's shape; resolution describes how many pixels it contains. Check both before export, then assess clarity at phone size. Create the edit on a 9:16 timeline when the intended result is a full-height vertical Reel. The timeline makes it easier to compose shots consistently and avoid an accidental horizontal master with large empty bands. The example 1080 x 1920 canvas is useful because it is a simple 9:16 export target and gives you enough room to review ordinary text and product details. It is not presented here as an Instagram minimum or maximum. Keep the original camera file separate from the export. Cropping a wide recording into a tall frame changes what is visible; increasing its pixel count does not recreate missing detail. If the subject is cut off, return to the framing decision rather than increasing the bitrate. If a phone preview looks soft, inspect the source focus, scaling, compression, and rendered file before assigning the cause to Instagram. A visually sharp still frame in an editor does not guarantee the compressed final video will remain legible. A cover image and the video are related assets with different checks. The cover may look good at full height yet lose the label or face in a smaller grid preview. Review the cover wherever your publishing surface shows it. The Reel itself needs playback review: movement, captions, audio, and end frame. Do not use the cover's pixel dimensions as a substitute for examining the video stream. - Write width before height so an export preset is unambiguous. - Use a 9:16 timeline for a full-height vertical composition. - Inspect the rendered video, not only the timeline or cover still. ## Read Meta's technical numbers in the right context **Answer:** Meta's public Reels Publishing API sample lists technical requirements for its API pathway and recommends 9:16; those values should not be repeated as universal Instagram app limits. In the Meta-maintained sample for API publishing, the documented container is MOV or MP4, the video codec is HEVC or H.264, and the listed frame-rate range is 23 to 60 frames per second. That same sample lists a maximum of 1920 horizontal pixels and recommends 9:16 even though its stated accepted aspect-ratio range is much broader. These are properties of the sample's API route. A creator editing in the Instagram app, a scheduler using a different integration, and an advertiser may encounter different controls or validation messages. Do not confuse a recommended composition with the bounds of an accepted file. Saying that 9:16 is recommended does not mean every other shape is rejected. Saying that an API accepts a broad range does not mean a landscape video will fill a vertical viewing surface attractively. The production decision is to make a deliberate full-height version when that is the desired presentation and to keep the original so a different crop can be prepared if another placement needs it. The API sample is also a reminder that dimensions are only one layer of validity. An export with the right width and height can still fail because of encoding, audio, rights, account eligibility, or a publishing workflow requirement. Check the current documentation for the exact route you use and read the specific upload error rather than assuming every rejection is a size error. This guide does not certify that a file will be accepted by Meta. - Meta API sample: MOV or MP4, HEVC or H.264, and 23 to 60 fps for that API route. - Meta API sample: 9:16 is recommended to reduce cropping or blank space. - Consumer app, scheduler, and ads eligibility require their own destination checks. ## Compose for the visible area, then preview every surface **Answer:** Keep critical words and faces away from vulnerable edges, but avoid treating an invented pixel margin as an official safe-zone rule. A full-height 9:16 file is not an unobstructed poster. The viewer may see account information, a caption, actions, and other interface elements over the video. Meta's Reels advertising page calls for key messages in a safe zone; it does not provide a single universal organic-Reel pixel margin on the source used here. The inner area in this guide's illustration is a visual reminder to inspect content on a phone, not a published Meta measurement. Place the most important text and product detail where it remains understandable if the top, bottom, or side is visually busy. Use a short opening line that can be read while the frame moves. If a call to action depends on a tiny label near the bottom edge, move it into narration, captions, or the accompanying text as appropriate. Watch the Reel from start to finish at phone size: animation can move a formerly safe label into an obscured area. Preview the actual upload in the target interface. Examine the full-screen player, cover treatment, and any grid or feed preview available for the account. Record which surface you checked. A creator should not promise the same crop on every surface when the presentation can change. If the preview reveals a problem, correct the composition in the editable project and export a new version; do not stretch the finished file as a shortcut. - Check the moving frames, not only the opening thumbnail. - Read every key label at phone size with the interface visible. - Record which preview surfaces were actually reviewed. ## Run an original export QA checklist **Answer:** Save an eight-check record for the final render: source, canvas, playback, visible content, audio, cover, destination, and approval. Use this checklist against the exported file that will be uploaded, not an earlier timeline render. In the record, include the filename, version, editor, export date, target account, and reviewer. That simple header prevents a clean technical test from being attached to the wrong file. If an item fails, note the exact frame or timecode and create a new export version rather than silently replacing the file under the same name. Check one, source: confirm the approved original footage and its usage rights. Check two, canvas: read the exported width and height and calculate the ratio; for a 1080 x 1920 example it is 9:16. Check three, playback: watch the entire rendered file, including the first and final seconds, and inspect for frozen frames, unintended borders, or abrupt cuts. Check four, visible content: inspect the moving text, faces, products, and disclosures at phone size with the destination's interface present. Check five, audio: listen to speech, music, silence, and transitions on a phone speaker as well as in the editor; confirm rights for every sound. Check six, cover: compare the selected cover with the full-height view and the smaller preview offered by the account. Check seven, destination: upload only through an authorized account or approved test path, read its warnings, and examine its processed preview. Check eight, approval: compare the final file and caption with the reviewed facts and record who accepted the exact version. After publication, a separate live check confirms what viewers actually received. The eight checks are an editorial method created for this page. They are not a list of Meta certification requirements. A format match answers only the shape question; it does not prove the content is accurate, rights-cleared, accessible, accepted, or live. Keep the failed check in the record so the next export fixes the actual issue. - 01 Source and rights; 02 width, height, and ratio. - 03 full playback; 04 phone-size content and interface overlap. - 05 audio and rights; 06 cover and smaller preview. - 07 destination processing; 08 approval of the exact version. ## Worked example: one 9:16 product demonstration **Answer:** A fictional 24-second lamp demonstration shows how a correctly proportioned export can still fail a content or preview check. North Lane Studio is a fictional business used only to illustrate the method. It is not a FluxGravity customer, and this page reports no upload, reach, engagement, or sales result. The approved brief says the video should demonstrate the lamp's adjustable arm and two visible desk positions. The team owns the footage and has approved the product name. No brightness measurement, medical benefit, discount, or customer endorsement is supplied, so none belongs in the Reel. The editor creates a 1080 x 1920 working timeline and makes a 24-second vertical draft from three original shots. The first shot shows the whole lamp and a short question. The second shows the arm moving from one position to another. The third returns to the complete desk so the viewer can understand the result. The chosen export dimensions are an example of 9:16 composition; this fictional exercise does not establish that any particular Instagram account accepted the upload. During the local phone-size review, the lower-third label in the second shot is difficult to read behind a simulated interface overlay. That is a deliberately constructed review finding, not an observed Instagram result. The editor moves the label toward the centre, renders version two, and reruns the eight checks. The reviewer then inspects the final video and cover separately. If an authorized account later uploads it, the team must record the actual processed preview and publication state before making a public success claim. The example illustrates why an original QA record is more useful than copying a dimension chart. The ratio was correct in both versions; the content check identified the problem. Keeping the two version names and the failed timecode makes the fix reviewable. A reader can apply the same method to a tutorial, event reminder, or product clip while substituting only facts and media they can verify. - Approved facts: adjustable arm and two filmed desk positions. - Example export: 1080 x 1920 pixels, 9:16, 24 seconds. - Constructed QA result: revise a lower-third label before any upload. ## Diagnose a Reel that looks wrong or fails to upload **Answer:** Identify whether the problem is the crop, rendered quality, cover, encoding, account path, or content approval before making another export. If the video has bars or a cropped subject, read the exported width and height and compare them with the editing timeline. A 9:16 wrapper can still contain a smaller horizontal image with bars inside it. Return to the original footage and reframe intentionally. If text is clipped, inspect the frame at the reported timecode and update the editable layout; scaling the entire exported video may make the text smaller and introduce a new problem. If the video looks soft, compare the source clip, editor preview, local export, and destination preview in that order. Record where the loss first appears. The cause may be source focus, aggressive scaling, export settings, or processing, and this guide has not reproduced a specific platform failure. If only the cover looks wrong, inspect the selected cover and smaller preview separately instead of re-encoding the whole video without evidence. If an upload is rejected, preserve the exact warning and confirm which publishing route was used. The Meta API sample has format, codec, frame-rate, duration, and file-size requirements for its route, but those values do not diagnose every app error. Verify the file against the current rules of the destination, including account eligibility and any rights or policy notices. Changing the aspect ratio without reading the message can waste time and make a previously good composition worse. - Bars or bad crop: inspect timeline and export dimensions. - Softness: compare source, local export, and processed preview. - Rejection: save the exact message and check the route-specific rule. ## Connect the Reel brief to an honest FluxGravity workflow **Answer:** Use FluxGravity to organize approved facts into a script, shot list, and review brief, then check the actual video file and publishing result in the tools that handle them. Start with the audience question, approved claims, available footage, forbidden claims, desired duration, and intended action. Ask for a short script that names the visual evidence for each line. That structure helps a reviewer distinguish a sentence supported by footage from a claim that merely sounds persuasive. The output remains a draft until the facts, assets, rights, and final production are approved. Copy-ready prompt: Draft a 9:16 Instagram Reel plan for [audience] about [topic] using only these approved facts: [facts]. Available footage: [shots]. Target duration: [duration]. Return a timecoded shot list, on-screen text, spoken lines, source for each claim, cover idea, caption draft, and the eight export QA checks from this guide. Mark missing facts as questions. Do not invent results, benefits, testimonials, or platform acceptance. Do not claim that the Reel has been uploaded or published. After the draft, create and inspect the video in the editing and publishing surfaces your team actually uses. FluxGravity's Instagram Post Size Checker can compare an uploaded still image or entered dimensions with reference shapes. It does not inspect a video stream, edit a video, or export a resized Reel. Use it for a cover still or an initial ratio reference only. Use the final video file's metadata and the destination preview for the video-specific checks, then retain the approved version and live URL if it is published. - Draft from approved facts and available footage. - Use the image checker for still images or entered dimensions only. - Verify the final video in the actual destination. ## Frequently asked questions ### What aspect ratio should I use for an Instagram Reel? Use 9:16 for a full-height vertical working canvas. Meta's Instagram Reels Publishing API sample recommends that ratio to avoid cropping or blank space. Check the actual preview for your account and publishing route. ### Is 1080 x 1920 mandatory for every Instagram Reel? No universal requirement is established by the sources used here. It is a practical 9:16 example canvas. The Meta API sample recommends the ratio but documents broader aspect-ratio acceptance for its API route. ### Can a file be 9:16 and still look wrong? Yes. It may contain letterboxing inside the frame, a poor crop, soft source footage, unreadable text, or important content hidden by interface elements. Review the rendered file and destination preview. ### What are the official Reel safe-zone pixels? This guide does not assert a universal organic-Reel pixel margin. Meta's Reels ads guidance asks advertisers to keep key messages in a safe zone, while actual overlays and previews should be checked in the destination surface. ### Does FluxGravity's Instagram size checker read video files? No. The current tool reads image dimensions locally or accepts width and height entered manually. It does not inspect, crop, or resize video. ### Which export checks matter after choosing the right dimensions? Review the approved source and rights, canvas, full playback, phone-size content, audio, cover, processed destination preview, and approval of the exact final version. ### Does passing this checklist guarantee Instagram will publish the Reel? No. It is an editorial QA method. Account eligibility, current upload rules, processing, rights, and platform decisions must be checked through the actual publishing route. ## Sources - [Meta: Instagram Reels Publishing API sample and technical requirements](https://github.com/fbsamples/reels_publishing_apis/blob/main/insta_reels_publishing_api_sample/README.md) - [Meta for Business: Instagram and Facebook Reels creative guidance](https://www.facebook.com/business/ads/facebook-instagram-reels-ads) ## Related pages - https://fluxgravity.io/guides/instagram-scheduling-tools - https://fluxgravity.io/guides/instagram-post-ideas ## Try FluxGravity Give FluxGravity one goal and receive finished work. https://app.fluxgravity.io/