Skip to content

docs: media limits catalog per content type with official specs - #22

Open
paulocastellano wants to merge 5 commits into
mainfrom
align-platform-media-limits
Open

docs: media limits catalog per content type with official specs#22
paulocastellano wants to merge 5 commits into
mainfrom
align-platform-media-limits

Conversation

@paulocastellano

@paulocastellano paulocastellano commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Companion to trypostit/trypost#353 align-platform-media-limits (Instagram Reel 300 MB, X 8 GB / 20 min tweet_video, Bluesky 2 000 000 B / 300 000 000 B + 10 min + MOV blocked, TikTok 4 GB / 10 min, Discord / Telegram explicit caps, server-side enforcement of GIF/MOV/size/duration on publish).

What changes

  • knowledge-base/media.mdx rewritten Buffer-style:
    • Cloud upload hard caps vs the tighter per-content_type cap
    • "What TryPost does to your files": PNG/WebP → JPEG on store, crop/fit/optimize on publish per network, video never transcoded, GIF and MOV gates
    • "Enforced on the server, not just in the editor": what publish/schedule re-checks (kind, GIF/MOV, size, duration when known), that drafts are never blocked, and that API uploads carry no duration
    • Size catalog table (image / video / duration) for all 20 content types
    • One block per network with size, duration, format, aspect and the official spec link; Bluesky cites the lexicon maxSize values and the 26 Aug 2026 10-minute announcement; X states the 8 GB / 20 min default (Premium 16 GB / 125 min) and that 1 GB is the Cloud cap; Instagram feed's 100 MB / 60 s is labelled as TryPost's conservative rule (Meta only documents the Reel spec; a single feed video publishes through the Reels container); TikTok 10 min with creator_info possibly lower
    • FAQs: ~900 MB Instagram video, long video on a feed post, "upload accepted but publish refused" (422 on platforms.<n>.content_type), Telegram URL 5/20 MB, Bluesky MP4 only
  • platforms/*.mdx (all 12): short "Media limits" table, same official link, pointer to Media. Bluesky / X / TikTok / Instagram rows carry the corrections above.
  • api-reference/endpoint/list-content-types.mdx: accepts_mov field; caps noted as already clamped to the instance upload cap and enforced server-side.
  • api-reference/endpoint/update-post.mdx: media compatibility is re-checked on scheduled / publishing with or without platforms[] (unlike the per-platform meta check).
  • ai/tools-reference.mdx: accepts_mov.

No new nav page. Every number matches ContentType::mediaRules() after the Cloud hard cap.

Based on docs/socials-workspaces-pricing (#20); retargets to main when that merges.

Expand knowledge-base/media.mdx Buffer-style: Cloud size catalog,
per-content_type size / duration / format with the official API page,
what TryPost does to images vs video as-is, and FAQs (900 MB Instagram,
feed video publishes as Reel, Telegram URL 5/20, Bluesky MP4 only).
Each platform page gets a short table and a pointer back to Media.
Document the new accepts_mov flag on GET /content-types and the MCP tool.
@paulocastellano
paulocastellano changed the base branch from main to docs/socials-workspaces-pricing September 12, 2026 01:17
Base automatically changed from docs/socials-workspaces-pricing to main September 12, 2026 01:19
…d document server-side enforcement

- Bluesky: lexicon decimal bytes, 10-minute limit with the official
  announcement as source, BLUESKY_VIDEO_MAX_BYTES note.
- X: 8 GB / 20 min tweet_video default (Premium 16 GB / 125 min); 1 GB is
  the Cloud cap, not an X limit; never amplify_video.
- TikTok: 10-minute API ceiling, creator_info may lower it.
- Instagram feed: 100 MB / 60 s is TryPost's conservative rule, single
  video publishes through the Reels container.
- New section on publish/schedule server-side checks (kind, GIF/MOV,
  size, duration) plus update-post and list-content-types notes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant