Answer: Postifys accepts reachable media URLs (with optional
proxyDownload) and still enforces its own temporary-media capacity. Provider caps below are the practical encoding targets - design fan-outs to the strictest destination in the set. Numbers are from official docs where cited; re-check before large encoding jobs.Postifys media handling
- Prefer public HTTPS media URLs; use
proxyDownloadfor Google Drive / Dropbox. - Large files can fail with temporary-media / size errors even when under a provider’s published cap - compress or stagger jobs.
- Async: Postifys acceptance ≠ final public post (especially TikTok inbox and YouTube processing).
Provider media limits (numeric)
How to choose one media file for multiple platforms
For a one-video-to-many workflow, start with the strictest destination instead of the largest one. A YouTube-ready file can be huge, but the same file may fail on Instagram, TikTok, or temporary media processing. For safest fan-out, create a short vertical MP4 variant for Reels, Shorts, and TikTok, then create a separate landscape or long-form variant only when YouTube needs it.
| Publishing target | Best starting format | Common issue to avoid | Postifys handling |
|---|---|---|---|
| Short vertical video across Instagram, Facebook, TikTok, and YouTube Shorts | MP4, H.264, AAC, 9:16, under the strictest duration and size limit | Assuming a YouTube-sized upload will work everywhere | Use one shared media URL only after checking platform-specific caps. |
| Long YouTube video plus social clips | Separate long-form YouTube file and shorter social cutdowns | Sending a 10+ minute file to short-form endpoints | Branch the workflow before publishing, then track each Postifys ID separately. |
| Image pins and link posts | Compressed JPG/PNG/WEBP with a stable public HTTPS URL | Private, expiring, localhost, or blocked URLs | Postifys rejects private/local URLs to protect production infrastructure. |
| Client-supplied media from Drive or Dropbox | Proxy-downloadable public share URL, then normalized media | Provider download pages instead of direct media content | Use supported proxy download behavior and test one item before bulk publishing. |
What this means in a real publishing workflow
Platform limits change and often depend on account type or publishing method. Use the comparison as a preflight guide, then validate important size, duration, aspect-ratio, and codec assumptions against the current destination response.
Recommended implementation
- Inspect the source file before upload.
- Apply the strictest shared encoding only where reuse is valuable.
- Keep platform-specific title and caption limits separate.
- Record provider errors so the comparison can be updated from real behavior.
How to verify the fix
MP4 with H.264 video, AAC audio, yuv420p, even dimensions, and faststart is a broadly compatible baseline, not a guarantee for every account and operation.
Operational check: Test with one item, confirm the final destination and Postifys history state, and only then enable the recurring workflow. Keep the returned Postifys ID beside the source row so every result remains traceable.
Related Postifys resources
API documentation · Error reference · n8n automation guide · Safe retry guide · Compatibility matrix
| Platform | Max size (typical API/docs) | Duration | Formats / notes | Source |
|---|---|---|---|---|
| Facebook Page video / Reel | Feed/resumable often up to ~1-1.75 GB depending on upload method | Reels API: 3-90 s (story Reel ≤60 s) | MP4 recommended; 9:16 / 1080×1920 for Reels | Meta Reels Publishing; Graph video edges for larger feed uploads |
| Instagram Reel (Graph) | 300 MB (Reels specs in IG media docs) | 3 s-15 min API max; Reels-tab eligibility often shorter / 9:16 | MOV/MP4; H.264/HEVC; AAC | IG User Media |
| YouTube upload | API: 256 GB max file | Up to 12 hours (channel verification required for >15 min in product UI) | video/*; Shorts usually ≤60 s vertical in practice |
videos.insert; YouTube Help |
| Pinterest image Pin | Web image: 20 MB | n/a | JPEG/PNG/WEBP/… - Postifys documents image Pins | Pinterest Pin specs |
| Pinterest video Pin (platform) | Ads/docs often up to 2 GB; organic help lists video length rules | Help center organic video: 4 s-5 min | MP4/M4V/(MOV on mobile); not claimed in Postifys product today | Pinterest Pin specs |
| LinkedIn member video | Organic native: up to 5 GB (Help for Pages) | Help: 3 s-10 min (desktop UI sometimes longer) | MP4 and listed codecs; Postifys = members, not Company Pages | LinkedIn video specs |
| TikTok Content Posting API | 4 GB | API init max 10 min (creator account may trim lower) | MP4/MOV/WebM; H.264 recommended; 23-60 FPS; 360-4096 px | TikTok media transfer guide |
Postifys capability note: TikTok supports approved Direct Post and optional Draft Upload. Pinterest video Pins and LinkedIn Company Pages are not claimed. Always match the Postifys account type in the compatibility matrix.
Fan-out encoding rule
- Pick destinations first.
- Encode to the strictest size/duration/aspect among them (often Instagram Reel or Facebook Reel for short vertical).
- If one network needs a different aspect, branch a second encode - do not stretch silently.
- Keep YouTube titles non-empty; keep TikTok completion steps explicit for inbox mode.
Related: compatibility matrix · temporary-media errors · unsupported formats · media docs · six-platform fan-out