Facebook Page Thumbnail Size: Exact Dimensions and Best Practices

Use a square Facebook Page profile image at least 320 × 320 pixels. Facebook turns that profile picture into circular thumbnails beside your Page name in posts, comments and other locations. Keep the important subject centered, leave margin around it, and check the image at a small size.

What size should a Facebook Page thumbnail be?

Prepare the source profile image at 320 × 320 pixels or larger. The 320 × 320 figure is a minimum source-image recommendation for quality; it is not a promise that Facebook will render the thumbnail at exactly 320 × 320 pixels.

Facebook describes the thumbnail as a smaller version of the profile picture shown beside your name in different places. The rendered size can vary by placement, screen size and interface. Facebook’s published help information does not specify one universal output dimension.

Asset	Recommended preparation	What Facebook does
Page profile image	Square, at least 320 × 320 px	Displays as a circular image in many contexts and resizes it for different placements
Thumbnail rendering	No separate upload required	Creates smaller versions beside the Page name
Page cover photo	Separate wide asset	Uses different cropping and sizing rules

How to design the image so it survives the crop

1. Start with a square canvas

Create a 1:1 image, preferably larger than the 320 × 320 minimum if you are exporting from a design tool. A larger source gives you room to edit and resize cleanly.

2. Keep the subject in the center

Place the logo, face or identifying symbol in the middle of the canvas. Treat the outer area as unsafe because the circular mask removes the corners.

3. Leave breathing room

Do not place a wordmark, face or icon against the edge. Padding makes the subject recognizable when Facebook reduces it to a small circle.

4. Avoid fine text

Small slogans and long names usually disappear at thumbnail scale. If text is necessary, use a short mark with thick, high-contrast lettering.

5. Use strong contrast

Make the foreground distinct from the background. Check the result on both light and dark surroundings because Facebook surfaces can differ.

6. Preview at small sizes

Export a preview at roughly 32–64 pixels and inspect it on a phone-sized layout. If you cannot identify the Page immediately, simplify the artwork before uploading.

Why the thumbnail may look different in each place

• Responsive layouts: desktop and mobile interfaces allocate different space to the profile image.
• Circular masking: corners of the square source are hidden.
• Scaling: Facebook generates smaller presentations for feeds, comments and other surfaces.
• Interface changes: placements can change as Facebook updates its products.

For these reasons, there is no single rendered “Facebook Page thumbnail size” you can design against. The controllable part is the source image: make it square, sharp and legible when reduced.

Profile image versus cover photo

A Page profile image and a Page cover photo are different assets. Do not use cover-photo measurements to prepare the thumbnail. The researched guidance reports cover-photo minimums and recommendations separately, while the profile-image guidance calls for a square source of at least 320 × 320 pixels.

If you are preparing a complete Page, create the profile image first, then design the cover independently for its wide, responsive crop.

Practical export checklist

• ☐ Canvas is square (1:1).
• ☐ Source is at least 320 × 320 pixels.
• ☐ Important content sits inside a centered safe area.
• ☐ Corners do not contain essential details.
• ☐ Text is short, bold and readable when reduced.
• ☐ Image remains clear after compression.
• ☐ You checked a circular preview at small size.
• ☐ You verified the result on both desktop and mobile.

Creating a thumbnail preview with code

If you need to review many candidate images, you can create a circular preview locally. This example uses Python and Pillow; it does not upload anything to Facebook.

from PIL import Image, ImageDraw

source = Image.open("page-profile.png").convert("RGBA")
source = source.resize((320, 320), Image.Resampling.LANCZOS)

mask = Image.new("L", (320, 320), 0)
draw = ImageDraw.Draw(mask)
draw.ellipse((0, 0, 319, 319), fill=255)

preview = Image.new("RGBA", (320, 320), (255, 255, 255, 255))
preview.paste(source, (0, 0), mask)
preview.save("facebook-thumbnail-preview.png")

Inspect the generated preview at 64 pixels as well as 320 pixels. This models the circular crop and helps reveal details that are too small to survive.

Or skip the browser setup

When you need screenshots of a Facebook Page or other web pages for documentation, QA or content review, ScreenshotNeo captures the page through one API request. It accepts the consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before the capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the verdict and billing status in X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.

See the ScreenshotNeo API documentation for all options. This basic call returns a WebP image:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo includes full-page capture, element selection, custom CSS and JavaScript, device presets, retina scale, waiting rules, blocking controls, cookies and headers, caching, signed links, asynchronous jobs, bulk capture and PDF output. The Free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000.

Create a free ScreenshotNeo account and start with 1,000 screenshots per month at no charge.

Troubleshooting common thumbnail problems

The logo is cut off

Cause: Important pixels are too close to the square edge and are removed by the circular mask.
Fix: Reduce the logo and add even padding on all sides.

The image looks blurry

Cause: The uploaded source is below the recommended minimum or has been enlarged from a low-resolution file.
Fix: Export a clean square source at 320 × 320 pixels or larger.

Text cannot be read

Cause: The text is too small for the thumbnail rendering.
Fix: Remove secondary words, increase weight and contrast, or use a symbol instead.

The profile image looks different on mobile

Cause: Facebook uses different responsive placements and rendering sizes.
Fix: Keep the composition simple and verify it at several small preview sizes.

The cover image was used as the thumbnail

Cause: Cover and profile assets have different purposes and proportions.
Fix: Upload a separate square profile image and keep the cover design wide.

FAQ

Is 320 × 320 pixels the displayed thumbnail size?

No. It is the minimum source-image guidance. Facebook can render the profile image at different sizes, and its help text does not define one fixed thumbnail output.

Can I upload a rectangular Page profile image?

Use a square source. A rectangular design gives Facebook less predictable cropping and can remove important content.

Should the logo touch the edge?

No. Leave a margin so the circular crop and small renderings do not cut into the mark.

Are Page profile and cover dimensions interchangeable?

No. They are separate assets with different shapes, placements and cropping behavior.

How do I know whether the image works?

Preview it as a circle at small sizes on both desktop and mobile layouts. Recognition at thumbnail scale is the practical test.