\n| Another format or placement<\/td>\n | Check its exact guide<\/td>\n | Do not copy a number from another row<\/td>\n | An objective, placement or media-type change needs a matching specification.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n These figures are current scoped recommendations, not a ranking of creative performance. The guide also lists separate technical requirements. Give the designer both the intended export and the applicable limits, then check the upload and preview. Do not reject a working asset solely because an unrelated format uses a different ratio.<\/p>\n Check the post-click experience separately. If the offer opens a website, form or conversation, the next step should explain the same outcome and make the intended action clear. A correctly sized image does not establish that the destination is ready or that a particular automation product supports the proposed workflow.<\/p>\n A useful specification answers four questions: which objective, which format, which placement and which media type? If one is unknown, identify it before copying dimensions into a brief. That avoids presenting a reasonable design example as an official requirement for a different campaign.<\/p>\n <\/p>\n Facebook Ad Size Pixels: A 2026 Placement Checklist<\/h2>\nUse dimensions as a production checklist. For the checked Awareness examples, plan the Feed image, Stories image or carousel card separately. Keep a source link with the brief, record the recommendation versus the minimum, and inspect the actual crop. Do not assume an accepted upload will look identical in every enabled placement.<\/p>\n Start With the Verified Placement<\/h3>\nFor an Awareness Feed image, the checked guide recommends 1440\u00d71800 pixels. For a Stories image it recommends 1440\u00d72560 pixels. Feed carousel guidance recommends at least 1080\u00d71080 pixels. These examples have different roles; confirm the exact campaign before turning any of them into a reusable template.<\/p>\n \n- Feed image example:4:5, recommended 1440\u00d71800 pixels for Awareness.<\/li>\n
- Stories image example:9:16, recommended 1440\u00d72560 pixels for Awareness.<\/li>\n
- Carousel example:1:1, recommended at least 1080\u00d71080 pixels for Awareness Feed.<\/li>\n<\/ul>\n
Design Reels for the Placement<\/h3>\nFor Reels, keep the current format guide separate from the image examples in this article. Meta\u2019s Reels information encourages vertical video, audio and attention to safe zones; it does not justify applying one Stories image requirement to every Reels or boost setup. Inspect the exact placement and its controls before exporting.<\/p>\n Check Meta\u2019s current Reels advertising guidance for that format. Do not treat a general best-practice page as a verified video-duration limit or an entitlement to use every media type in every account.<\/p>\n Match the Ad to the Conversation<\/h3>\nSize alone does not make an ad effective. The first visible message should name the same outcome the customer receives after clicking. If the ad offers a faster quote, clearer support, or a product guide, the next screen and Messenger Bot conversation should continue that promise without making the customer hunt for it.<\/p>\n Keep the main offer readable and avoid making a dense image the only explanation. For video, review the visual message as well as any audio. These are design checks to reduce ambiguity, not promises of improved engagement or a claim that one composition will outperform another.<\/p>\n Pre-Publish Quality Check<\/h3>\n\n- Prepare the asset shapes required by the actual selected formats, rather than a compulsory two-file pack.<\/li>\n
- Select the placements you actually intend to buy.<\/li>\n
- Review every placement preview for cropped faces, hidden text, and covered buttons.<\/li>\n
- Confirm that the destination or conversation repeats the advertised offer and has a useful next step.<\/li>\n
- Compare measured outcomes before increasing spend; a good preview alone does not prove business performance.<\/li>\n<\/ol>\n
Keep eligibility, presentation and campaign results separate. A file can meet a technical requirement without communicating an offer clearly, and a clear design can still need a different export for another placement. Use the actual guide and preview to decide the next change.<\/p>\n <\/p>\n Verified Image and Carousel Dimensions<\/h2>\nThe following table separates official checked examples from unverified formats. Its values are scoped to the Awareness objective shown in Meta\u2019s guide. Do not silently transfer the image figures to Feed video, Messenger inventory, collection ads or a different setup path. Sources: Meta Feed image guide<\/a>, Meta Stories image guide<\/a> and Meta Feed carousel guide<\/a>.<\/p>\n \n\n\n| Format and placement<\/th>\n | Ratio<\/th>\n | Resolution or next check<\/th>\n | How to use it<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Facebook Feed image<\/td>\n | 4:5<\/td>\n | 1440\u00d71800 pixels recommended<\/td>\n | Use the checked Awareness image guidance, including its technical limits.<\/td>\n<\/tr>\n | \n| Facebook Feed video<\/td>\n | Check the current video guide<\/td>\n | No video resolution certified by the image example<\/td>\n | Match media type, objective and placement before export.<\/td>\n<\/tr>\n | \n| Facebook Stories<\/td>\n | 9:16<\/td>\n | 1440\u00d72560 pixels recommended<\/td>\n | Use the checked Awareness Stories image guidance and safe-zone preview.<\/td>\n<\/tr>\n | \n| Facebook Reels<\/td>\n | Check the current Reels format<\/td>\n | Do not inherit a Stories image specification<\/td>\n | Confirm the media and setup path available to this campaign.<\/td>\n<\/tr>\n | \n| Messenger placement<\/td>\n | Check the exact placement<\/td>\n | No Messenger specification certified here<\/td>\n | Keep placement separate from a click-to-message destination.<\/td>\n<\/tr>\n | \n| Click-to-message destination<\/td>\n | Depends on where the ad appears<\/td>\n | Use that placement\u2019s actual specification<\/td>\n | Opening a conversation does not establish an inbox creative size.<\/td>\n<\/tr>\n | \n| Carousel cards<\/td>\n | 1:1<\/td>\n | At least 1080\u00d71080 pixels recommended<\/td>\n | Checked Awareness Feed carousel;2\u201310 cards and media-specific limits.<\/td>\n<\/tr>\n | \n| Collection hero creative<\/td>\n | Check the collection placement guide<\/td>\n | No collection dimension certified here<\/td>\n | Confirm the hero and supporting content requirements separately.<\/td>\n<\/tr>\n | \n| Existing landscape asset<\/td>\n | Measure its ratio<\/td>\n | Check selected placement acceptance<\/td>\n | Do not call an old 1200\u00d7628 template a universal current requirement.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Technical requirements for the checked examples matter too. Feed image lists JPG or PNG, a 30 MB maximum, minimum width 600 pixels and minimum height 750 pixels for 4:5. Stories image lists JPG or PNG,30 MB maximum and 500 pixels minimum width. Feed carousel lists 2\u201310 cards, image maximum 30 MB and video maximum 4 GB. Confirm the matching guide before release.<\/p>\n Decide how many assets to produce from the formats you will actually buy. A one-placement campaign may not need a broad creative pack, while multiple placements may need carefully reviewed adaptations. Do not treat \u201ctwo assets\u201d as a universal minimum or a proven cost-saving strategy.<\/p>\n For the checked Feed carousel, the guide recommends square cards. Keep the intended order and visual continuity understandable, then inspect every card. Consistent design is an editorial choice; it does not establish that a carousel will perform better than another format.<\/p>\n If you select collection ads, inspect their own current guide and preview rather than borrowing a hero size from a Feed image or Stories row. Review the supporting product material as well as the first asset. This article\u2019s checked carousel example does not certify a collection setup.<\/p>\n For video, check the current video-specific format and placement. Do not infer a best-performing aspect ratio, duration or audio strategy from an image specification. Review how the idea is communicated in the actual environment and use measured campaign results to judge performance.<\/p>\n For a brief based on the three verified Awareness examples, record these checks:<\/p>\n \n- Feed image: recommended 1440\u00d71800 pixels,4:5; distinguish that recommendation from the 600\u00d7750 minimum.<\/li>\n
- Stories image: recommended 1440\u00d72560 pixels,9:16; check the preview\u2019s overlay areas.<\/li>\n
- Feed carousel: recommended at least 1080\u00d71080 pixels,1:1; confirm 2\u201310 cards.<\/li>\n
- Other formats: inspect their own current specification instead of copying a verified row into an unrelated setup.<\/li>\n<\/ul>\n
Choose Creative by Placement, Not by a Universal Winner<\/h2>\nUse the following distinctions to decide what to inspect, not to predict which ad will win. A recommendation for a particular format helps production; performance still depends on the campaign and its actual results.<\/p>\n Feed image recommendations are not video requirements<\/h3>\nMeta\u2019s checked Awareness Feed image guide recommends 4:5. Its recommendation is 1440\u00d71800 pixels; its technical minimum is 600 pixels wide and 750 pixels high for that ratio. Keep those categories separate when briefing a designer. Neither figure proves a better conversion rate or certifies the same choice for Feed video.<\/p>\n If an existing square or landscape asset is working, do not replace it solely because a guide recommends another shape for a different setup. First confirm the intended placement, inspect the current presentation and decide whether there is a demonstrated problem. Preserve the evidence needed to compare the change.<\/p>\n Stories and Reels need separate format checks<\/h3>\nThe checked Awareness Stories image guide recommends 9:16 at 1440\u00d72560 pixels. It also advises keeping important creative away from interface overlays. That supports a Stories image brief; it does not establish a universal Reels video requirement or make a differently cropped asset unacceptable in every setup.<\/p>\n Keep Instagram\u2019s in-app boost path separate from a campaign created in Ads Manager. Read the actual current requirements and any rejection message for the selected path. This guide does not certify a universal 90-second limit or promise that changing a duration will resolve a rejection.<\/p>\n Messenger destination and Messenger placement are different choices<\/h3>\nAn ad can appear in one placement and open a conversation after the click. Identify both separately. Do not describe all click-to-message creative as inbox inventory or assume a square,4:5 or 9:16 asset is accepted everywhere. Read the current specification for the actual surface selected in your campaign.<\/p>\n Check what happens after the click as well as the creative preview. Confirm that the first question, expected response and route to a person match the advertised offer. Weak replies alone do not establish that automation, the asset ratio or any one part of the conversation is the cause.<\/p>\n Carousel is about card consistency more than creative drama<\/h3>\nThe checked Awareness Feed carousel guide allows 2\u201310 cards and recommends 1:1 at least 1080\u00d71080 pixels. Its current examples distinguish image and video limits. Use that scoped specification for production, then inspect every card\u2019s crop, text and destination rather than assuming that dimensional consistency proves campaign success.<\/p>\n If a sequence relies on a particular order, inspect the actual card-order controls available in your setup and the preview of the result. Do not assume an optimization switch exists for every format or account. Make the story understandable without hiding necessary context on an easily missed card.<\/p>\n Collection ads need their own review<\/h3>\nReview the current collection format and the supporting product information as a separate setup. A polished opening asset does not certify the supporting material, destination or campaign eligibility. If something looks wrong, record the actual observation before attributing it to a catalog, crop or format.<\/p>\n Existing landscape assets need context, not an automatic rebuild<\/h3>\nA landscape asset may be useful in a particular campaign, but its historical use does not make it a current universal specification. Check the actual placement\u2019s guide and whether the current preview shows a problem. Do not describe a different ratio as an improvement until the relevant result has been tested.<\/p>\n The practical rule is to identify the format first, use its current scoped recommendation and confirm the preview. A ratio is not a universal performance ranking, and a click-to-message destination is not a substitute for a placement specification.<\/p>\n Check File Limits, Text and Interface Overlays<\/h2>\nSize is not just ratio. Real facebook advertising size decisions include safe zones, text density, asset quality, duration, and whether the ad is going to sound-on or sound-off environments. Get the ratio right and ignore everything else, and you can still end up with a weak ad.<\/p>\n Use higher-resolution exports, but design around the ratio<\/h3>\nRatio describes a shape; pixel dimensions describe the exported resolution. A larger file does not automatically fix a bad crop, and upscaling does not restore information missing from the original. Use the matched guide\u2019s recommendations and limits, inspect the source quality and compare the uploaded preview before changing another setting.<\/p>\n Keep text lighter than you think you need<\/h3>\nKeep important copy readable in the actual preview. Do not rely on an old image-text percentage rule or turn a text recommendation into a universal acceptance limit. Use the available copy fields to explain the offer, while keeping essential conditions understandable wherever the ad is shown.<\/p>\n As an editorial check, ask whether the visual has one clear subject and whether the offer remains understandable at the displayed size. Add detail where the format provides room for it, not in tiny text that is essential to understand the claim. This is a design review, not a performance guarantee.<\/p>\n Design video for sound-on, but never depend on sound alone<\/h3>\nReview video with and without audio so you know what information each version communicates. If captions or visual explanations are needed, verify them in the finished placement. Do not infer a guaranteed engagement improvement from a general recommendation to use sound.<\/p>\n Respect vertical safe zones<\/h3>\nFor the checked Stories image, Meta\u2019s guide recommends leaving space for interface elements. Inspect logos, prices and calls to action in the actual preview; an export can have the recommended dimensions while an overlay still covers important information. Do not apply a fixed safe-zone percentage from another placement without checking it.<\/p>\n Verify duration for the exact video format<\/h3>\nA video-duration limit belongs to a particular format and placement, not to every ad. The checked Feed carousel page lists 1 second to 240 minutes for its video cards; that is not a Reels, Stories or in-app boost limit. Keep only the information needed to communicate the offer, and verify the relevant acceptance rule separately.<\/p>\n Use this production checklist before exporting any new ad set:<\/p>\n \n- Does the creative have a feed version in 4:5 or 1:1?<\/li>\n
- Does it have a true 9:16 version if Stories or Reels are enabled?<\/li>\n
- Is the main hook readable in the first second or first screen?<\/li>\n
- Are logos, prices, and CTA elements clear without living in unsafe top or bottom zones?<\/li>\n
- Is the image text light enough to stay readable across crops?<\/li>\n
- Does the video still make sense with sound off?<\/li>\n
- Have you previewed the asset inside the exact placements you plan to use?<\/li>\n<\/ul>\n
If you want one sentence to remember from this section, it is this: the right facebook advertising size is the ratio that fits the placement plus<\/strong> a layout that still works once Meta wraps its own interface around your creative.<\/p>\nSize For Fb Ads: The Complete 2026 Guide<\/h2>\nUse the next table as a planning worksheet. Its purpose is to identify the specification that must be checked, not to label one size as the best for every campaign goal. A goal alone does not determine the creative format or placement.<\/p>\n \n\n\n| Planned use<\/th>\n | First specification to check<\/th>\n | Additional check<\/th>\n | What this does not establish<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Feed image campaign<\/td>\n | The matching Feed image guide<\/td>\n | Objective and destination<\/td>\n | The checked Awareness recommendation is not a video or all-objective rule.<\/td>\n<\/tr>\n | \n| Lead-generation campaign<\/td>\n | Actual format and placement<\/td>\n | Form and destination requirements<\/td>\n | A campaign goal does not certify one image size.<\/td>\n<\/tr>\n | \n| Click-to-message campaign<\/td>\n | The placement where the ad appears<\/td>\n | The conversation it opens<\/td>\n | A Messenger destination is not automatically Messenger inbox inventory.<\/td>\n<\/tr>\n | \n| Reels campaign<\/td>\n | Current Reels media guide<\/td>\n | Selected setup path and objective<\/td>\n | Do not copy Stories image dimensions or a boost limit unconditionally.<\/td>\n<\/tr>\n | \n| Feed carousel campaign<\/td>\n | The matching carousel guide<\/td>\n | Card count and media limits<\/td>\n | The checked Awareness example does not certify every carousel placement.<\/td>\n<\/tr>\n | \n| Existing testimonial creative<\/td>\n | Selected format and placement<\/td>\n | Permission and claim support<\/td>\n | A suitable crop does not validate a testimonial or its result.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Choose a format because it suits the intended customer task and the campaign setup you can actually use. Then copy the current scoped specification into the brief. There is no size in this article that is declared the winner for every advertiser or every goal.<\/p>\n For a message destination, inspect the opening question and handoff alongside the creative. A weak response rate can have several causes; it does not prove that the image is fine or that automation is the missing fix. Use actual conversation and campaign observations before changing either.<\/p>\n Keep the inspection focused: placement presentation, offer, destination and actual outcome are separate observations. If the destination or handoff is untested, leave that item open instead of diagnosing a conversion problem from the image alone. A proportionate test should answer one specific question.<\/p>\n If several placements are genuinely required, organize the work as an asset checklist:<\/p>\n \n- One asset matched to the chosen Feed format, where applicable.<\/li>\n
- A separately checked vertical asset for the intended full-screen format, where applicable.<\/li>\n
- Square cards only when the selected carousel or another checked format calls for them.<\/li>\n<\/ul>\n
Reuse the offer and visual identity where that helps production, while adapting the composition to each checked format. This is an organizational option, not proof that a specific pack is cheaper or performs better. Keep every adaptation traceable to the actual requirement and preview.<\/p>\n Step-by-Step Setup and Configuration in 2026<\/h2>\nUse the following as a proposed production workflow. The exact controls available in Ads Manager can differ, so do not invent a missing button or assume that an old menu sequence applies to your account. Start by inspecting the current setup before changing it.<\/p>\n \n- Identify the actual objective, format, placement and destination before giving a designer dimensions.<\/li>\n
- Open the matching current specification and record recommended resolution, technical minimums and media limits separately.<\/li>\n
- Choose placements for the campaign you intend to run; do not enable broader coverage solely because this guide mentions it.<\/li>\n
- Prepare only the adaptations needed by the selected formats, with a clear source and version for each asset.<\/li>\n
- Use customization controls only where available and relevant to an observed crop or presentation issue.<\/li>\n
- Preview every enabled placement before publishing.<\/strong> This is non-negotiable. Feed, Reels, Stories, Messenger, and any desktop placements you care about should all be reviewed visually.<\/li>\n
- Watch text truncation and UI overlap.<\/strong> Check the first frame, logo visibility, pricing callouts, subtitle position, and button clarity. This is where safe-zone problems show up.<\/li>\n
- Name versions so you can connect the actual asset and placement with later measurements; a name alone does not establish which variation won.<\/li>\n<\/ol>\n
Here is a tighter build process for a small team that wants speed without chaos:<\/p>\n \n\n\n| Step<\/th>\n | What to do<\/th>\n | What to avoid<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Creative brief<\/td>\n | Define one hook, one offer, one action, and the primary placement family.<\/td>\n | Writing separate messages for every placement before the core idea is proven.<\/td>\n<\/tr>\n | \n| Master design<\/td>\n | Build the selected format\u2019s recommended shape and resolution.<\/td>\n | Treating an old template as a universal current requirement.<\/td>\n<\/tr>\n | \n| Adaptations<\/td>\n | Create the second ratio version by moving layout blocks, not by squeezing the same canvas.<\/td>\n | Auto-cropping without checking where text lands.<\/td>\n<\/tr>\n | \n| Upload<\/td>\n | Match the file to its checked format and placement.<\/td>\n | Letting a story asset double as a feed ad without review.<\/td>\n<\/tr>\n | \n| QA<\/td>\n | Preview mobile first, then desktop if used.<\/td>\n | Approving creative from the design file alone.<\/td>\n<\/tr>\n | \n| Measurement<\/td>\n | Compare results by ratio and by placement breakdown.<\/td>\n | Lumping all asset shapes together and guessing what drove results.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n If the ad leads to a customer conversation, verify that path as its own acceptance item. A better preview is not evidence of better replies, and an accepted upload does not prove an operating automation. Review the exact task and current product before relying on it.<\/p>\n Common Problems and How to Fix Them in 2026<\/h2>\nUse these symptoms to choose an observation, not to diagnose a campaign from its appearance alone. Record the selected placement, uploaded asset, displayed message and preview before changing anything. No fix below is a verified outcome for every account or campaign.<\/p>\n \n\n\n| Problem<\/th>\n | What to inspect<\/th>\n | A check to try<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Your feed ad looks tiny on mobile<\/td>\n | Compare the selected placement and crop with the uploaded asset.<\/td>\n | Compare a 4:5 alternative in the actual mobile Feed preview before changing the campaign.<\/td>\n<\/tr>\n | \n| Your Story or Reel ad has huge empty bars<\/td>\n | Inspect the original ratio and the placement\u2019s actual crop or padding.<\/td>\n | Compare a correctly scoped vertical export with the actual preview; do not assume bars alone prove a cause.<\/td>\n<\/tr>\n | \n| Your CTA or price is covered in Stories<\/td>\n | Check the placement preview for interface overlays covering those elements.<\/td>\n | Move key text and logos toward the center of the frame and preview again.<\/td>\n<\/tr>\n | \n| Your carousel feels messy<\/td>\n | Compare each card\u2019s source file, crop and alignment.<\/td>\n | Compare cards with the current carousel recommendation and inspect crop and alignment before making a correction.<\/td>\n<\/tr>\n | \n| Your Messenger ad gets clicks but weak replies<\/td>\n | Review both the ad promise and the actual conversation; neither is cleared by click counts.<\/td>\n | Check the actual opening question and route to a person; change only a demonstrated mismatch.<\/td>\n<\/tr>\n | \n| Your boosted Reel fails review or setup<\/td>\n | Read the exact rejection or setup message for the selected boost path.<\/td>\n | Check that path\u2019s current duration, aspect-ratio, media-rights and feature restrictions before revising the asset.<\/td>\n<\/tr>\n | \n| Your image looks blurry after upload<\/td>\n | Compare the source export and uploaded preview before assigning a cause.<\/td>\n | Compare the original quality and uploaded preview, then correct the demonstrated export problem.<\/td>\n<\/tr>\n | \n| Your ad works in feed but not in Messenger preview<\/td>\n | Inspect the actual Messenger placement and its asset requirements separately.<\/td>\n | Check the actual placement guide and available customization controls before altering the asset.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nProblem: a boosted post does not behave like an Ads Manager build<\/h3>\nAn in-app boost and an Ads Manager campaign are different setup paths. Compare the controls actually available to your account before choosing one for the job. Moving a campaign does not, by itself, establish why a crop failed or guarantee that another setup will solve it.<\/p>\n Problem: Meta preview looks acceptable, but the live ad still feels off<\/h3>\nAn acceptable preview does not establish campaign performance or identify the cause of a disappointing result. Compare the actual delivered placement and measured outcome with the creative version used. Keep eligibility, visual presentation and business results as separate checks.<\/p>\n Problem: your copy is doing the work your visual should be doing<\/h3>\nAs a design check, ask whether the visual communicates the offer without requiring dense body text. Make the main object, scene or message clear and keep essential context readable. This is an editorial production suggestion, not evidence that one composition is the best-performing option for your campaign.<\/p>\n If you use AI assistance for creative ideas, verify every factual claim, image right and product promise yourself. Generated copy or an attractive image does not replace the format guide or the placement preview. Do not present an imagined dashboard or result as a customer\u2019s actual experience.<\/p>\n Comparison With Alternatives: What Works Better<\/h2>\nCompare production approaches by their workload and suitability for your actual placements. The table describes organizational tradeoffs, not a study of which pack performs best. Do not rebuild a sound campaign merely to match one of these labels.<\/p>\n \n\n\n| Approach<\/th>\n | What you build<\/th>\n | Possible use<\/th>\n | Main weakness<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Single square system<\/td>\n | One 1080 x 1080 asset<\/td>\n | Very small teams, quick tests, square-friendly product ads<\/td>\n | Needs a separate check for formats that use another shape.<\/td>\n<\/tr>\n | \n| Single feed-first system<\/td>\n | One 1080 x 1350 asset<\/td>\n | A deliberately selected feed-format exercise<\/td>\n | Still needs adaptation for true full-screen placements<\/td>\n<\/tr>\n | \n| Dual-ratio system<\/td>\n | One 1080 x 1350 asset plus one 1080 x 1920 asset<\/td>\n | A campaign using those two checked shapes<\/td>\n | Requires more production discipline than a single-file workflow<\/td>\n<\/tr>\n | \n| Full placement pack<\/td>\n | 1:1, 4:5, 9:16, and optional 1.91:1 variants<\/td>\n | Several genuinely required formats<\/td>\n | More QA time and more chances to create inconsistent messaging<\/td>\n<\/tr>\n | \n| Legacy landscape-first system<\/td>\n | Mostly 1200 x 628 creative<\/td>\n | An existing asset whose selected placement has been checked<\/td>\n | May need a different export for another format; check rather than assume.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n A dual-ratio pack is one production option: prepare a feed-oriented version and a full-screen vertical version, then inspect both. Compare the workload and measured campaign results with a square-only or broader pack rather than assuming one system wins for most brands.<\/p>\n Compare website-first and message-first destinations using the outcome your campaign is intended to produce. A conversation can suit a question-led purchase, but that does not establish that it will outperform a landing page. Keep the offer consistent and use measured results for the decision.<\/p>\n Compare the complete customer path without assuming a result from one ratio. Keep the offer consistent, use the actual delivered placement and measure the outcome that matters to the business. A conversation destination can be one option, but it is not automatically superior to a website or form.<\/p>\n If the next step is a business conversation, Browse Our Tutorials<\/a> and verify the relevant workflow. A tutorial is supporting context, not evidence that a product supplies every feature a campaign might need.<\/p>\nSafety, Privacy, and What to Watch Out For<\/h2>\nReview rights, claim support and private information as well as dimensions. A technically valid file can still contain an unsupported promise or information that should not be public. Keep those checks independent of any judgment about whether the crop looks good.<\/p>\n Do not let crop changes hide legal or trust-critical information<\/h3>\nIf your ad has financing terms, eligibility notes, disclaimers, regulated-product language, or time-sensitive pricing, those details cannot live in the edge zones of a 9:16 asset or the bottom sliver of a 4:5 frame. A crop that hides the important part can create review problems, user confusion, or flat-out trust damage.<\/p>\n Do not upload private conversations or user data carelessly<\/h3>\nBefore using a conversation screenshot or testimonial, confirm permission and remove information that should not be shared. Recreating an illustration does not make a fabricated customer result acceptable. Label simulations honestly and avoid showing names, phone numbers, account details or private messages.<\/p>\n Watch the Special Ad Category edge cases<\/h3>\nCheck the current policy and setup requirements for the actual campaign category and jurisdiction. A general image-size guide does not determine eligibility or legal compliance. Do not infer that a creative passing dimensional checks is approved for a regulated subject.<\/p>\n Brand safety matters more with video placement expansion<\/h3>\nIf you are leaning into broader placement delivery, especially with video, remember that your ad can surface in more contexts than a manual-feed-only setup. That is one reason to review where your brand is comfortable appearing, not just whether the asset fits dimensionally.<\/p>\n Use this quick safety checklist before launch:<\/p>\n \n- No copyrighted assets or music you do not have rights to use.<\/li>\n
- No private customer information visible in screenshots or testimonials.<\/li>\n
- No critical legal or pricing information sitting near crop-prone edges.<\/li>\n
- No fake UI buttons, fake notifications, or misleading interface overlays.<\/li>\n
- No assumptions that a feed-safe asset is automatically story-safe.<\/li>\n<\/ul>\n
Do not release an asset while necessary conditions are unreadable or private customer details remain visible. Correct the specific issue and recheck the affected placement. A technically sharp image is not a substitute for permission, factual support or a clear offer.<\/p>\n Keep the Specification Current<\/h2>\nThe current checked Awareness examples provide distinct image and carousel recommendations. Do not invent a year-over-year performance story from those figures. When using this article later, confirm the exact official page again before treating a number as a current requirement.<\/p>\n Keep the specification source, selected objective, format and placement with the creative brief. If an account control or official requirement changes, revisit the affected item rather than rebuilding every asset. A sound existing campaign does not need an unsupported change merely because another guide uses a different example.<\/p>\n Automation and resizing controls do not remove the need to inspect the final creative. Use the options actually available in the account and verify their output. Do not assume that an automated adjustment preserves a disclaimer, makes a result better or grants access to an unavailable placement.<\/p>\n Future format changes are uncertain. Build a process that can accommodate them: retain the source asset, record the checked specification and keep the intended message clear. Do not turn a prediction about advertising automation into a current campaign requirement.<\/p>\n For a conversation destination, maintain the same discipline after the click. Confirm the available workflow, answer support and human-assistance path before relying on them. Dimensions are one part of production, not a promise of qualified leads or revenue.<\/p>\n\nNeed the post-click chat flow to match the ad?<\/h3>\nChoose the customer-conversation setup that matches the follow-up you have verified. If you are considering Messenger Bot for your business, Check Current Pricing<\/a> and confirm that the current plan supports the particular workflow you need. A subscription is not a guarantee of ad performance.<\/p>\n<\/section>\n\nFrequently Asked Questions<\/h2>\nWhat size does Meta recommend for a Facebook Feed image ad?<\/h3>\nFor the checked Awareness objective, Meta\u2019s current Feed image guide recommends 4:5 at 1440\u00d71800 pixels. It separately lists minimum width 600 pixels and minimum height 750 pixels for 4:5. Confirm the exact objective and format; an image recommendation is not a universal video specification.<\/p>\n What size should a Facebook Stories image use?<\/h3>\nThe checked Awareness Stories image guide recommends 9:16 at 1440\u00d72560 pixels, JPG or PNG, with a 30 MB maximum and 500 pixels minimum width. Inspect important text and logos against the actual interface overlays. Do not transfer these figures automatically to Reels video or an in-app boost.<\/p>\n What are the checked Facebook Feed carousel requirements?<\/h3>\nFor the Awareness example, the current guide recommends 1:1 and at least 1080\u00d71080 pixels, with 2\u201310 cards. It lists image maximum 30 MB and video maximum 4 GB. Check the selected placement and media type rather than treating these as every carousel\u2019s requirements.<\/p>\n Does opening Messenger determine the ad\u2019s image size?<\/h3>\nNo. The destination and the placement where the ad appears are different choices. Identify the actual format, objective and placement, then use their current guide. A click-to-message destination alone does not certify an inbox, Feed or Stories specification.<\/p>\n Should I replace an existing ad just because another ratio is recommended?<\/h3>\nNot without checking the relevant setup and an actual problem. A recommendation is not proof of better business performance. Compare the current asset, scoped specification and placement preview, and change only what the evidence supports.<\/p>\n<\/section>\n | | | | | |