How we source and verify specs

A value is shown only when the platform's own official page states it. Every value carries its source link and the date we last checked it.

Rules

1. Official sources only. Platform help centres and official developer documentation. No third-party guides, templates or blog posts.
2. Quote, don't infer. We record what the page says (for example "recommended" vs "minimum"). We don't calculate or round values the source doesn't give.
3. Dated. Each verified value has a last_verified date and a source_url in specs.json.
4. Unverified means no number. If we can't confirm a value — for example because the help page needs JavaScript or blocks automated access — it's shown as "Not yet verified" with no number, and with a link to the official page where we know it.
5. Developer docs are labelled. Where a value comes from developer documentation (for example TikTok's Content Posting API guide), the spec label says so.
6. Re-checked. We re-fetch sources regularly; any value older than 60 days is re-verified, and every change is logged in the changelog.

Current status

34 values verified, 9 not yet verified (as of 2026-10-16).

Spotted a change on an official page? The changelog lists every update.