Verifying Social Media Image Dimensions and Safe Zones per Platform

Every social media image dimension you have memorised is already out of date. The fix is not a better cheat sheet. The only durable way to keep image sizes straight across platforms is to stop trusting third-party blogs and verify each number against the platform's own published specification. That document is the only source that changes when the renderer changes. You verify by opening the relevant help page, reading the current aspect ratio and pixel recommendation, and then checking whether your design's critical content sits inside the safe zone, not at the trim. That method, not a screenshot, not a saved PDF, not a colleague's memory, is what you are about to learn.

Platforms crop images differently between the Android feed renderer and the iOS feed renderer, and they change those crops without notice. A portrait post that displays perfectly on an iPhone may lose its top and bottom margins on a Pixel. No amount of pixel-perfect design can prevent that. What you can control is where you put your content. The safe zone is the area inside the trim edge where platform-level cropping will not touch your content. Anything outside it is at risk. Design so that all text, logos, and faces fall inside that zone. Treat the rest of the canvas as bleed the platform may discard.

This is not a theoretical concern. The failure mode is called a safe-area violation: text or critical elements get trimmed off in production because the designer placed them at the trim edge without confirming the platform's tolerance. The fix is boring and reliable. After you export your JPEG or PNG, load the image into the platform's own preview tool. Use the Facebook Sharing Debugger, the LinkedIn Post Inspector, the X Card Validator, and the Pinterest Rich Pins Validator. Look at the crop at actual render size. If the preview tool shows your headline cut off, move it inside the safe zone and re-export. Do not guess. Do not rely on a design tool's mockup that shows a perfect crop. The mockup is an idealisation. The preview tool is the renderer.

Shared Images and Link Previews

Facebook's help page is the Meta Business Help Center, and it changes on an annual schedule whether you are ready or not. The shared image recommendation is 1200 × 630 pixels at a 1.91:1 aspect ratio. The link preview image must be at least 200 × 200 pixels or the platform will not generate a preview at all. None of these numbers is a law of physics. Each is a convention the platform can and does revise, which is why you check the source before every campaign, not after.

The practical failure case is the link preview. You design a 1200 × 630 image, upload it, and share the link on Facebook, only to see the preview crop your headline. The cause is that you placed the text too low, inside the area the renderer trims. The fix is to use the Facebook Sharing Debugger before you post. It shows you exactly what the crawler sees. If the preview is wrong, fix the image, not the post. When the help page itself is down or you are on a deadline at 1am, the fallback is to keep all text within the central 600-pixel band of the image. That has been a reliable safe zone across every renderer variation since 2019.

Profile and Cover Photos

The profile picture is a 1:1 square, and the cover photo is a 2.7:1 banner. Event covers and group covers both use 1.91:1.

Posts, Stories and Reels

Instagram is where the safe-zone problem bites hardest, because the platform crops aggressively and changes its crops without a changelog. The square post is 1:1, the portrait post is 4:5, and the landscape post is 1.91:1. Both Stories and Reels are 9:16. The profile picture is 1:1 and appears as a circle in the app. Your square image needs a central focal point with at least 20 percent padding from each edge, or the circle crop will cut off a face. The Reels cover photo is also 9:16. It is the one place where the platform lets you choose a frame, but the choice is constrained to frames from the video itself. You cannot upload a separate cover image unless you build it into the first frame of the video.

The Carousel Problem

The failure case is the carousel. Instagram's feed renderer shows the first image of a carousel at a 4:5 crop in the grid, but the full carousel may display at 1:1 or 9:16 depending on whether the user taps. If you design all carousel images at 4:5 and the platform decides to show a 1:1 preview, you lose the sides. The verification method is to check the Instagram Help Center for the current specifications, then test your carousel on both Android and iOS accounts before posting to a business profile. The safe zone for any Instagram image is the central 80 percent of the canvas. Anything outside that is a gamble.

Shared Images and Link Previews

LinkedIn is the platform where designers most often get caught by file-weight limits and old dimensions. The shared image recommendation is 1200 × 627 pixels at 1.91:1, and the maximum file size for images is 5 MB. If your PNG is heavier than that, which it will be if you exported a hero image with a gradient, LinkedIn rejects it silently. Your post goes out without the image. The shared link preview image is 1200 × 627 pixels. LinkedIn uses the LinkedIn Post Inspector to generate the preview, so you must check that tool before you publish.

Profile and Company Photos

The personal profile photo is 1:1, the personal background photo is 4:1, the company logo is 1:1, and the company cover photo is 5.91:1. That last ratio is unusual and fits no standard canvas. The failure case is the company cover photo. The 5.91:1 ratio is so wide that most templates do not include a safe zone guide, and designers routinely place the company name and tagline at the edges, only to see them cropped on a laptop viewport. The fix is to keep all text within the central 60 percent of the canvas and to export at exactly 1584 × 396 pixels, which is the pixel dimension that corresponds to 5.91:1 at the platform's display resolution. The help page is LinkedIn Help, and it is updated on an annual schedule. If you are designing a company page, check it before every refresh, not just when you remember.

X uses a 1:1 profile photo, a 3:1 header photo, and a 1.91:1 card image. The X Card Validator is the only tool that shows you what the card will look like in a feed. YouTube's channel banner has a minimum safe area of 1546 × 423 pixels for text and logos, which means the full banner is larger but the critical content must fit inside that central band. TikTok's in-feed video minimum resolution is 540 × 960 pixels, and its carousel images can be 9:16 or 1:1. Pinterest's standard Pin is 2:3, the square Pin is 1:1, and the board cover is 1:1. Snapchat's ad image is 9:16 with a maximum file size of 5 MB, and geofilters must be PNG with a transparent background. WhatsApp Status is 9:16. Each of these platforms publishes its own help page, and each of those pages changes without notice.

The one thing every one of these platforms shares is the verification requirement. You cannot design once and reuse, because the aspect ratios are different enough that a single crop will fail somewhere. The batch resizing tools, Adobe Photoshop with its image processor, Canva with Magic Resize, Figma with export presets, and Sketch with artboards, all get you to the right pixel dimensions. None of them tells you whether the platform will accept the file. That is why the platform-specific validators exist, and why you must use them. A tool that checks dimensions is not the same as a tool that checks the render. The failure case is always the same: you upload a perfectly optimised JPEG, and the platform crops it, compresses it, or rejects it. You have to go back to the source file.

Every social media platform accepts JPEG and PNG, and most accept GIF. That is where the commonality ends. The colour space is sRGB across every platform on this page. If you design in Adobe RGB or ProPhoto RGB, the platform will convert the image to sRGB and the desaturation will be noticeable, especially in skin tones. The maximum file size ranges from 5 MB to 20 MB depending on the platform. The failure mode is silent rejection: the platform does not tell you the file was too heavy, it just does not upload it. The compression artefacts from a 40 KB hero image may be invisible at 100 percent zoom but obvious at feed size. Export at the pixel dimensions the platform specifies and then check the file weight before upload.

The practical rule is to keep the file weight as low as possible without visible artefacts, and to test at the actual render size on a phone, not on a desktop monitor. The 72-ppi logical resolution convention is irrelevant to social media. The platform determines the pixel dimensions and the pixel density is whatever the viewer's screen has. What matters is the pixel count, not the PPI value in the file metadata. A 1200 × 630 image exported at 72 PPI and the same image exported at 300 PPI are identical to the platform. The metadata is a label, not a fact about the image's information content.

Open Graph is the metadata layer that tells a platform what image to use when you share a link. The recommended aspect ratio is 1.91:1. If you do not specify an Open Graph image, the platform crawls the page and picks the first image it finds, which is the wrong one. The failure case is a link preview that shows a screenshot of the page instead of your carefully designed hero image. Worse, the platform chooses an image from the middle of the page that has no relation to the content. The fix is to include an og:image meta tag in the page header, reference a file that is at least 1200 × 630 pixels, and test the URL with the platform's validator before you share it.

The Open Graph specification does not change often, but the platforms that consume it change their rendering behaviour on their own schedule. A preview that looks correct on Facebook today may look different next month, because the platform updates its renderer without a changelog. The verification method is the same as for everything else on this page: open the platform's own preview tool, check the crop, and adjust. The preview tool for Open Graph is the same tool you use for regular posts, so the workflow is identical.

You now have the numbers, but the numbers are not the point. The method is the point, and the method has four steps. First, open the platform's own help page and read the current specification. If the page has not been updated in 18 months, treat the numbers with suspicion and test with a live post. Second, design to the safe zone, not the trim, and keep all critical content inside the central 80 percent of the canvas. Third, export at the platform's recommended pixel dimensions, not at a size you think looks good. Fourth, test with the platform's validator before you publish, and check the result on both Android and iOS if the platform has a native app.

This method costs you five minutes per platform and prevents the most common failure modes: a safe-area violation that trims your headline, a file-weight rejection that drops your image silently, and a crop that looks fine on desktop but wrong on mobile. The reason the method works is that it removes the guesswork. You are not relying on a third-party summary that may be outdated. You are going to the source the platform itself controls. When the source is wrong, or when the platform has not updated its documentation, the method includes a fallback: test with a live post, look at the result, and adjust.

What is the most common mistake when setting social media image sizes? Placing text or logos outside the safe zone. The platform crops the trim, and your content ends up cut off. Design inside the central 80 percent of the canvas.

How often should I check the platform's help page? Before every campaign, and at minimum every quarter. The platforms update their specifications on their own schedule, and the numbers you have may already be superseded.

Why does my image look different on Android versus iOS? The feed renderer differs between the two platforms. The pixel dimensions are the same, but the crop and the compression are not. The safe zone is the only reliable placement guide.

What do I do if the platform's help page is down? Use the validator tool, which shows the actual render. If both are unavailable, design conservatively: keep critical content central, and test with a live post before you commit.

Adobe Photoshop, Canva, Figma, and Sketch all offer batch resizing for social media images, and each has its own export presets. Photoshop's image processor handles folders of images, Canva's Magic Resize creates multiple sizes from one design, Figma's frames with export presets generate multiple assets at once, and Sketch's artboards do the same. These tools are useful, but they are not the source of truth. A tool that resizes to 1200 × 630 pixels does not know whether that is the current size for Facebook. It knows only what you tell it. The tools are a convenience, not a substitute for checking the platform's help page.

The batch tool that matters is the platform's own preview tool, because it is the only one that knows what the renderer will do. The Facebook Sharing Debugger, the LinkedIn Post Inspector, the X Card Validator, and the Pinterest Rich Pins Validator all show you the render before you publish. If your batch resizing tool produces an image that the validator crops, the tool is not wrong. Your safe zone is. The workflow is resizing first, then validation. Validation is the step that cannot be skipped.

Every specification here is flagged as changeable, and the sources are the platforms themselves. The numbers are a snapshot. They may be superseded by the time you read this. The verification method is the only thing that is durable, and it is the only thing you can rely on. The platform's help page is the source, the validator is the test, and the safe zone is the guardrail.

The honest caveat is that no method can protect you from a platform that changes its renderer overnight. Even the safe zone is only as good as the platform's current behaviour, and the platform may change it without notice. The best you can do is design conservatively, verify before you publish, and accept that social media image specifications are a moving target. What works today may not work next month. The only reliable response is to check, test, and adjust.