[Publish] Image resizing

Each social network has its own image file size limit. If the image you upload is larger than the limit for that social network, we'll convert it to a smaller size to ensure it can be published. Only one image attribute (width or height) will be adjusted and the other will scale automatically. This ensures that the original aspect ratio will be kept.

The table below outlines the file size limit for each social network, along with the sizes your images will be transformed too if they're too big. Please note, the file sizes listed below are specifically for static images, and do not apply to GIF files. The maximum file size for GIFs is 3MB.

Social Network File Size Limit Size Transformed To
Facebook
4MB 3000 pixels tall
Instagram
8MB 1920 pixels wide
Twitter
3MB 1024 pixels wide
LinkedIn 10MB 4746 pixels wide
Pinterest 10MB 600 pixels wide

Notes:

  • You may be able to upload larger images when creating posts natively. The file size limits mentioned in the table above are the limits when posting through the social networks' API. For example, Twitter's native file size limit is 15MB, while through the API, it's 3MB.
  • Image resizing will only take place on the web version of Buffer Publish. If you're scheduling via a mobile device (iOS or Android), the maximum file upload size is 10MB.
  • For Twitter specifically, if the image does not need to be resized, Buffer Publish will still check that the image is smaller than 8192 x 8192 pixels, since this is Twitter's maximum allowed dimension. If it's bigger than that, your image will be resized to be just a little smaller.
  • LinkedIn has shared that the optimal size for images to achieve consistency across various share methods, pages, and experiences, is 1200 x 627 pixels. This image size should prevent cropping and scaling across formats.
  • Buffer Publish does not currently resize GIF files, and the maximum file size is 3MB.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.