What video resolution to use for social media: platform requirements and our calculation
What YouTube, VK Clips, Instagram Reels and TikTok ask for — from their own documents: resolution, frame rate, codec and the ceiling on the weight of the file.
What video resolution to use for social media is a question with no single answer: each platform has its own requirements, and they do not match. YouTube adapts the player to any proportions, Instagram sets a minimum of 720 pixels and 30 FPS, VK Clips ask for 9:16 and 1080×1920. Below is a summary from the primary sources of the platforms and our calculation of how much a minute of such a clip weighs.
Resolution and format for each platform
The platforms describe their requirements in different ways, and the answers have to be collected from several documents — the resolution, the codecs and the sound, the ceiling on the weight of the file. YouTube splits its documentation between the recommended upload encoding settings and a separate page about resolution and aspect ratios; Instagram publishes a help page on the Reels size and, separately, the API specifications for the upload; VK keeps the requirements of a clip in a FAQ entry; TikTok describes the uploaded file in the author tools. The requirements are also written in different units: some pages name the resolution classes, others the recommended bitrate for each class, and others the limits for the uploaded file. Below is a summary from the primary sources; the requirements change, so they are worth re-reading before a delivery.
| Platform | Resolution and proportions | Frame rate | Length and weight |
|---|---|---|---|
| YouTube | 1920×1080 (1080p), 1280×720 (720p), 3840×2160 (4K); standard proportions 16:9 | 24, 25, 30, 48, 50, 60 fps | 8 Mbit/s on 1080p, 5 Mbit/s on 720p, 35–45 Mbit/s on 4K |
| VK Clips | 1080×1920 (9:16) | 60 FPS supported | from 3 seconds to 3 minutes, up to 1 GB |
| Instagram Reels | minimum 720 pixels; proportions from 1.91:1 to 9:16 | minimum 30 FPS | via the API — up to 300 MB |
| TikTok | 720×1280 or higher | not named in the upload requirements | up to 30 minutes, less than 10 GB |
The table shows the main thing: the vertical 1080×1920 suits every platform in the list, and there is no overlap of the bitrate requirements for any pair — each has its own numbers. YouTube does not restrict the proportions at all: when a vertical or a square file is uploaded, the player adapts itself. VK Clips, on the contrary, requires vertical: 9:16, 1080×1920, from 3 seconds to 3 minutes, a maximum of 1 GB, with Full HD and 60 FPS supported. Instagram Reels sets the lower bound rather than a recommendation: a minimum of 720 pixels, a minimum of 30 FPS, proportions from 1.91:1 to 9:16. The frame rate is where the requirements part again: YouTube asks you to encode and upload at the rate the material was shot at and names 24, 25, 30, 48, 50 and 60 fps, VK Clips support 60 FPS, Instagram Reels set a minimum of 30 FPS, and TikTok name no frame rate at all. The practical consequence: a clip that satisfies one platform is not automatically ready for another. The vertical frame with a moderate bitrate is accepted by all of them, but the bitrate to aim for, and in some cases the very format, is decided by the platform you upload to.
| Platform | Container | Video codec | Sound |
|---|---|---|---|
| YouTube | MP4 | H.264, High Profile, progressive scan, 4:2:0 | AAC-LC or Opus, 48 kHz |
| Instagram Reels (upload via the API) | MOV or MP4 | H.264 or HEVC, progressive scan, closed GOP, 4:2:0 | AAC, up to 48 kHz, 1–2 channels |
| TikTok | MP4 or WebM | not named | not named |
| VK Clips | not named | not named | not named |
The file requirements of Instagram are published for the upload via the API: the container MOV or MP4, the video codec H.264 or HEVC with progressive scan, a closed GOP and 4:2:0, AAC sound up to 48 kHz in 1–2 channels, a frame rate of 23–60 FPS, a VBR video bitrate up to 25 Mbit/s, audio at 128 kbit/s, and a file of up to 300 MB. For TikTok only the requirement to the uploaded file is published — MP4 or WebM, a resolution of 720×1280 or higher, up to 30 minutes and less than 10 GB — and the requirements name neither the codec, nor the sound, nor the frame rate. VK Clips name neither the container, nor the codec, nor the sound: there only the proportions, the resolution, the length and the weight are set. The result is that the depth of the descriptions differs: YouTube and the Instagram API specifications name the container, the codec and the audio, TikTok names only the container of the uploaded file, and VK Clips name none of them. Where the requirements are silent, the check is done by the upload itself: the platform accepts the file or rejects it with its own reason. That is why the format table is read together with the requirements table, and not instead of it.
How to check a file against the platform
A file is checked against a list before the delivery: the resolution and the proportions, the frame rate, the codec and the container, the weight of the file. The platform itself cuts the first two lines, the third sets the compatibility, and the weight is the only item of the list that can be calculated before the render. Everything else is settled by the upload: the platform either accepts the file or rejects it, and the reason for the rejection is its own. The order of the lines matters for the time it takes to fix a rejected file: a change of the resolution, the codec or the weight means a new render, and that is why these lines are checked before anything is rendered.
The order of the check is simple: first the resolution and the proportions — if they do not pass, the platform will reject the file; then the frame rate — YouTube directly requires encoding and uploading at the rate the material was shot at; then the codec and the container; and the weight last. The weight is the only item of the list that can be checked by calculation before the render: with a known bitrate and a known runtime the size of the file is calculated by formula, and not chosen by re-encoding the finished clip. The calculation takes the runtime and the bitrate that the platform recommends, and returns the weight that this runtime produces. It does not replace the check of the proportions, but it removes the last unknown from it, and it decides how long the runtime may be.
To understand what comes out, we encoded our own test signal 1920×1080 at 25 fps, 30 seconds long, in ffmpeg 9.0.2 — a separate file for every configuration. The source is synthetic: a test pattern without detail and movement, so the numbers that come out of it are a lower bound for real footage, and not a forecast for it. The rows of the table follow the export ladder protocol, so each of them can be reproduced from it.
| Configuration | File size | Bitrate | What it means |
|---|---|---|---|
| H.264, CRF 23 | 20 558 332 bytes | 5.48 Mbit/s | Full frame 1920×1080 |
| Vertical 1080×1920, H.264 CRF 23 | 8 346 717 bytes | 2.23 Mbit/s | Vertical frame |
| 4K 3840×2160, H.264 CRF 23 | 44 092 600 bytes | 11.76 Mbit/s | 4K frame |
The difference between the rows is bigger than it looks: in our measurement the vertical weighs 8 346 717 bytes against 20 558 332 bytes of the full frame — 2.5 times lighter — while the 4K, on the contrary, pulls 44 092 600 bytes. The rows compare the size of the file at the same CRF, and they say nothing about how the picture looks: the quality of the image was not measured. A caveat: the vertical and the 4K were obtained by an upscale from 1080p, and not by a native resolution, and the source was a synthetic test pattern without detail and movement. Our numbers are therefore a lower bound, and not a forecast for live material.
It is more reliable to calculate the weight from the bitrate that the platform itself recommends. The size formula is simple: size = bitrate × time ÷ 8 bit/B. By the YouTube recommendations a minute of a clip on 1080p (8 Mbit/s) weighs 60 MB, on 720p (5 Mbit/s) — 37.5 MB, and our vertical frame by our own measurement gives 16.7 MB per minute — because the source was empty. These numbers are not comparable with each other: the first two are planned weights at the bitrates the platform recommends, and the third is what our own measurement gave for a minute of the test signal. The same calculation works in the other direction: knowing the limit of the platform on the weight of the file, divide the limit by the bitrate and you get the maximum runtime of the clip. Read the estimate in the same order — the bitrate of the platform, the runtime, the limit — and every line of it can be checked before the render.
Separately about the delivery: different platforms need different versions of the file, and not one universal version. In our editing work a render for YouTube/VK/Reels means separate versions per platform, and the parameters of each version are set by the requirements of the platform, and not by the wish to make the file lighter. The same material is rendered separately for each of them, and the versions differ in the resolution, in the frame rate and in the target weight.
Frequently asked questions
Which resolution should I choose?
The vertical 1080×1920 — a working option for every platform in our table: it fits VK Clips, Reels, TikTok and YouTube, where the player adapts vertical clips itself. Instagram Reels will not accept anything below 720 pixels, and YouTube recommends 1080p with a bitrate of 8 Mbit/s and 720p with 5 Mbit/s. If in doubt, take 1080×1920 and calculate the weight from the bitrate of the platform.
Do I have to deliver in 4K?
For social media — not necessarily: in our measurement 4K costs 44 092 600 bytes against 20 558 332 bytes of 1080p at the same CRF, and our 4K is an upscale from 1080p, and not a native resolution. For YouTube as a platform with a large screen 4K makes sense, and its recommended bitrate there is 35–45 Mbit/s. The question is therefore not the resolution itself, but the screen the clip is watched on.
How much does a social media clip weigh?
It is calculated from the bitrate of the platform: a minute on 1080p by the YouTube recommendations — 60 MB, on 720p — 37.5 MB. By our measurements on the test signal a minute of the vertical frame came out at 16.7 MB, but that is a lower bound: on live material the bitrate is higher. The limits of the platforms matter too: VK Clips — up to 1 GB, Instagram via the API — up to 300 MB, TikTok — less than 10 GB.
What to read next
Need this done as a project?
We take on projects like this — with the same settings we walk through in this piece.