viral-video-platform-specs
Complete platform upload specifications for viral video creation across TikTok, YouTube Shorts, Instagram Reels, Facebook Reels, Snapchat Spotlight, and Twitter/X. PROACTIVELY activate for: (1) Platform-specific video encoding, (2) Upload requirements lookup, (3) Multi-platform export, (4) File size optimization, (5) Aspect ratio conversion, (6) Duration limits, (7) Audio requirements, (8) Caption/subtitle specs, (9) Thumbnail requirements, (10) Quality vs compatibility trade-offs. Provides: Comprehensive spec tables, FFmpeg presets per platform, optimal encoding settings, file size calculators, batch export workflows, and 2025-2026 platform-specific algorithm insights.
What this skill does
# Viral Video Platform Specifications Use this skill to choose export settings for TikTok, YouTube Shorts, Instagram Reels, Facebook Reels, Snapchat Spotlight, Twitter/X, Pinterest, LinkedIn, and mobile-browser playback. This SKILL is a lean orchestrator; detailed platform tables, commands, and recipes are preserved in `references/platform-details-and-recipes.md`. ## Quick Reference | Platform | Aspect | Recommended resolution | Practical duration | Max size | Default codec | |---|---:|---:|---:|---:|---| | TikTok | 9:16 | 1080x1920 | 21-34s | 287 MB iOS | H.264 + AAC | | YouTube Shorts | 9:16 | 1080x1920 | 50-59s | 256 GB | H.264 or VP9 | | Instagram Reels | 9:16 | 1080x1920 | 7-30s | 4 GB | H.264 + AAC | | Facebook Reels | 9:16 | 1080x1920 | 15-30s | 4 GB | H.264 + AAC | | Snapchat Spotlight | 9:16 | 1080x1920 | <=60s | 300 MB | H.264 + AAC | | Twitter/X | 9:16, 16:9, 1:1 | 1080x1920 | <=140s | 512 MB | H.264 + AAC | ## Universal Social Export Baseline ```bash ffmpeg -i input.mp4 \ -vf "scale=1080:1920:force_original_aspect_ratio=decrease,pad=1080:1920:(ow-iw)/2:(oh-ih)/2:black,setsar=1,fps=30" \ -c:v libx264 -preset medium -crf 22 -profile:v high -level 4.1 \ -c:a aac -b:a 192k -ar 48000 -ac 2 \ -pix_fmt yuv420p -movflags +faststart \ output_social.mp4 ``` Adjust loudness, duration, bitrate, and metadata per platform from the reference file. ## Core Workflow 1. Verify `ffmpeg -version`; prefer current stable builds for security and codec fixes. 2. Identify target platform(s) and whether the video is native-app upload or mobile-browser playback. 3. Normalize to vertical 9:16 unless the platform or campaign calls for square/horizontal. 4. Use H.264/AAC for the broadest acceptance. Use VP9 only when intentionally targeting YouTube/WebM. 5. Apply platform loudness targets: TikTok/Reels often around -10 to -12 LUFS; YouTube around -14 LUFS; Facebook around -13 LUFS. 6. Keep `-pix_fmt yuv420p` and `-movflags +faststart` for compatibility. 7. Verify output with `ffprobe` before upload. ## Key Gotchas - All major social platforms re-encode uploads; high-quality H.264 is usually a better upload source than HEVC/AV1 for social delivery. - For web/mobile-browser playback, profile/level, `yuv420p`, and faststart matter more than platform upload limits. - Keep captions and UI out of unsafe top/bottom regions, especially lower 35% on Reels-style interfaces. - Two-pass bitrate control is useful when a platform file-size ceiling is strict. ## Reference Map - `references/platform-details-and-recipes.md` - Full preserved reference: per-platform spec tables, FFmpeg presets, two-pass examples, multi-platform export script, file-size calculation, codec comparison, mobile-safe playback, color grading, text/caption readability, verification commands, sources. ## Related Skills - `viral-video-animated-captions` - CapCut-style caption generation - `viral-video-hook-templates` - Hook patterns and retention tactics - `ffmpeg-animation-timing-reference` - Timing, readability, sync, and platform pacing - `ffmpeg-command-syntax` - Correct option placement
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".