> ## Documentation Index > Fetch the complete documentation index at: https://www.ayrshare.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Social Media Image & Video Requirements > Reference image and video requirements for Bluesky, Facebook, Google Business Profile, Instagram, LinkedIn, Pinterest, Reddit, Telegram, TikTok, X & YouTube. ## Image and Video Posting Requirements When publishing a post to the social networks, it is important to follow each network's requirements. By following these guidelines, you can ensure your post is accepted by the social networks and reaches the intended audience. Please see the [post](/docs/apis/post/post) endpoint for additional details. ### Accepted File Types Files have an accepted file ending type (extension), such as jpg, jpeg, png, webp, gif, mp4, mov, or avi, with content-types such as image/jpeg or video/mp4. Additionally, LinkedIn accepts file types with the following extensions: ppt, pptx, doc, docx, and pdf. If the media URL has special characters, e.g. ñ, please encode the special characters before sending. Please see below for details on each network. **Automatic image format conversion.** WebP, HEIC, HEIF, and AVIF source images are automatically converted to JPEG before posting to platforms that don't accept them natively. WebP is converted for Instagram, LinkedIn, TikTok, Google My Business, Threads, and Snapchat; HEIC, HEIF, and AVIF are converted across all supported platforms. Conversion runs transparently at send time, so you can submit any of these formats via `mediaUrls` and Ayrshare will handle the format on the destination platform's behalf. The per-platform "supported formats" lists below describe what each network ultimately accepts on the wire; you do not need to convert beforehand. See [Image Format Conversion Errors](/docs/errors/errors-ayrshare#image-format-conversion-errors) for the failure modes (codes 450, 451, 452), and [Image Metadata and Content Credentials](/docs/media-guidelines/overview#image-metadata-and-content-credentials) for what happens to embedded metadata when an image is converted. ### **Maximum Images** Max images accepted per platform in a single post: ### **Maximum Videos** Only ***one*** video is allowed per post for Bluesky, Facebook, Instagram, LinkedIn, Pinterest, Telegram, Threads, TikTok, X/Twitter, and YouTube. Reddit does not yet support videos. Please be sure your video URL ends in an accepted video extension such as .mp4 or .mov, depending upon the network. For example: If your video is a signed URL or cannot end in an accepted video extension, you can use the [`isVideo`](/docs/apis/post/overview#video-extension) parameter when publishing the post. We recommend for larger video files over 50 MB create a scheduled post with the `scheduleDate` parameter for async processing. Be sure to also check the upload speed of your media URLs to prevent timeouts at the social networks. If the media file cannot be downloaded within approximately 5 minutes a time out will likely occur. ### Standard Social Video Requirements Each social network has different video requirements. If you want a video that can be published to social networks such as X/Twitter, Instagram, Facebook, and TikTok use the following standards: **Dimensions:** 1080 x 1920 px **Length:** 60 seconds **Size:** 50 MB **Format:** MP4 **Example Portrait Video:** `https://img.ayrshare.com/random/portrait5.mp4` You may also create specific sized video for networks such as YouTube that accept longer and larger files. Please see below for details of each network. See how to [create random videos](/docs/quickstart#random-image) for your testing. ### Content Type **When posting,** be sure the `content-type` is set appropriately, e.g. image/png, image/jpg, or image/jpeg. ### Secure URLs When posting your own media URL, the link must be secure by using SSL and starting with `https://` ### Social Network Media Requirements ## Image Metadata and Content Credentials Images frequently carry embedded metadata: an ICC color profile, an XMP packet, EXIF camera data, or a [C2PA](https://c2pa.org/) Content Credentials manifest. When an image is generated or edited with an AI tool, the AI disclosure normally lives in the XMP packet as the `Iptc4xmpExt:DigitalSourceType` property, and often inside a C2PA manifest as well. Ayrshare re-encodes an image to JPEG when the destination network won't accept the source format, as described under [Accepted File Types](/docs/media-guidelines/overview#accepted-file-types) above. A re-encode rewrites the file, so this section states exactly what Ayrshare carries across, what it drops, and what each network does with the result. Videos are never re-encoded and their metadata is untouched. ### Metadata Retained on Conversion ### Metadata Not Retained Don't rely on a converted image to prove authorship or tamper-evidence. If a verifiable C2PA signature is a requirement, publish the image in a format the destination network accepts natively so that no conversion takes place. ### When Conversion Happens If you need certainty that no re-encode will happen, supply JPEG or PNG. ### What Each Network Does With the Metadata Retaining the metadata is only half the journey. Each network decides independently whether to keep it on ingest and whether to render an AI label. The results below come from live posts published in August 2026 with no platform AI flag set, so the embedded metadata was the only possible signal: | Network | AI disclosure kept | ICC color profile kept | AI label rendered | | --------- | ----------------------------------------- | ---------------------- | --------------------------- | | Facebook | Yes | Yes | Yes — shown as "AI content" | | Instagram | Yes | No — stripped | Yes — shown as "AI info" | | Threads | Yes | Not measured | No label is rendered today | | LinkedIn | No — image metadata is stripped on ingest | No — stripped | No | Meta keeps the disclosure consistently across Facebook, Instagram, and Threads, but renders the label per surface: Facebook and Instagram show it, Threads currently does not. The two columns are independent, and Instagram is the reason it's worth saying so: it keeps the AI disclosure while discarding the color profile. That's also why WebP and AVIF images are converted to standard sRGB instead of being given a profile to carry — a profile only helps on a network that keeps it, whereas correct sRGB color is correct everywhere. **Provenance metadata does not survive LinkedIn's image processing.** LinkedIn removes embedded metadata when it ingests an image, so the `Iptc4xmpExt:DigitalSourceType` disclosure is not present on the published image and no AI label is applied. Don't treat embedded metadata as an AI-disclosure mechanism for LinkedIn. Networks not listed above were not measured. Network behavior can change without notice, so treat the table as observed behavior rather than a guarantee. **Instagram `autoResize` discards the disclosure.** When a post uses [`instagramOptions.autoResize`](/docs/apis/post/social-networks/instagram#auto-image-resize), the image is resized to 1080×1080 by a separate step that writes a new file and carries no metadata forward — so the AI disclosure, the ICC profile and any C2PA manifest are all absent from the image Instagram receives, regardless of what the source carried. If the disclosure needs to reach Instagram, supply an image that already meets Instagram's aspect-ratio requirements and leave `autoResize` off. ### Uploading Media Directly [`POST /media/upload`](/docs/apis/media/upload-media) stores your bytes verbatim. Nothing is re-encoded and all metadata — including EXIF and any C2PA manifest — is stored exactly as supplied. The retention behavior above applies only when an image is published to a network that requires a different format.