--- title: "Video Aspect Ratios Explained: 16:9, 9:16 and 1:1" description: Explore video aspect ratio basics, including 16:9 aspect ratio, 9:16, and 1:1, and find the best aspect ratio for video on any platform. image: https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-22-2026-07-30-18-6643-AM.jpeg --- [![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us) [๐Ÿ“˜Learn โ–พ](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [CDN Fundamentals](https://blog.blazingcdn.com/cdn-fundamentals?hsLang=en-us) [By Content Type](https://blog.blazingcdn.com/by-content-type?hsLang=en-us) [Advanced Concepts](https://blog.blazingcdn.com/advanced-concepts?hsLang=en-us) [Glossary](https://blog.blazingcdn.com/glossary?hsLang=en-us) [โšก Web Performance](https://blog.blazingcdn.com/web-performance?hsLang=en-us) [๐ŸŽฌVideo & Streaming โ–พ](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [๐Ÿ”ด Live Streaming](https://blog.blazingcdn.com/live-streaming?hsLang=en-us) [๐Ÿ“บ VOD & OTT](https://blog.blazingcdn.com/vod-ott?hsLang=en-us) [๐Ÿ’ฐ Bandwidth & Costs](https://blog.blazingcdn.com/bandwidth-costs?hsLang=en-us) [๐Ÿญ Other Industries โ–พ](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [๐Ÿ“บ Media & Broadcasting](https://blog.blazingcdn.com/media-broadcasting?hsLang=en-us) [๐Ÿ’พ Software & SaaS](https://blog.blazingcdn.com/software-saas?hsLang=en-us) [๐Ÿ—๏ธ DevOps & Cloud Infra](https://blog.blazingcdn.com/devops-cloud-infra?hsLang=en-us) [๐Ÿ“š AdTech & Advertising](https://blog.blazingcdn.com/adtech-advertising?hsLang=en-us) [๐ŸŽฎ Gaming & Esports](https://blog.blazingcdn.com/gaming-esports?hsLang=en-us) [๐Ÿ“ฑ Mobile Apps & Developers](https://blog.blazingcdn.com/mobile-apps-developers?hsLang=en-us) [๐Ÿค– AI & Machine Learning](https://blog.blazingcdn.com/ai-machine-learning?hsLang=en-us) [๐Ÿ›๏ธ Enterprise & Corporate](https://blog.blazingcdn.com/enterprise-corporate?hsLang=en-us) [๐Ÿ“š E-Learning & EdTech](https://blog.blazingcdn.com/e-learning-edtech?hsLang=en-us) [๐ŸŸ๏ธ Sports & Live Events](https://blog.blazingcdn.com/sports-live-events?hsLang=en-us) [๐Ÿ’ฐ Pricing & Costs โ–พ](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [Provider Pricing](https://blog.blazingcdn.com/provider-pricing?hsLang=en-us) [Cost Optimization](https://blog.blazingcdn.com/cost-optimization?hsLang=en-us) [Decision Support](https://blog.blazingcdn.com/decision-support?hsLang=en-us) [โšกCompare โ–พ](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [Provider Comparisons](https://blog.blazingcdn.com/provider-comparisons?hsLang=en-us) [Strategy Comparisons](https://blog.blazingcdn.com/strategy-comparisons?hsLang=en-us) [Ratings & Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [๐Ÿ“Š Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [๐Ÿ”’ Security โ–พ](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [Attack Protection](https://blog.blazingcdn.com/attack-protection?hsLang=en-us) [Encryption & Access](https://blog.blazingcdn.com/encryption-access?hsLang=en-us) [Video & DRM Security](https://blog.blazingcdn.com/video-drm-security?hsLang=en-us) [๐Ÿ“ Case Studies](https://blog.blazingcdn.com/case-studies?hsLang=en-us) [๐Ÿ”Œ Integrations](https://blog.blazingcdn.com/integrations?hsLang=en-us) [๐Ÿ› ๏ธ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [Get Started](https://blazingcdn.com/sign-up-contact-form/) [Learn](https://blog.blazingcdn.com/en-us/tag/learn) [Video - Video & Streaming](https://blog.blazingcdn.com/en-us/tag/video-video-streaming) [Learn - By Content Type](https://blog.blazingcdn.com/en-us/tag/learn-by-content-type) # Video Aspect Ratios Explained: 16:9, 9:16 and 1:1 Vadym Borovskyi Oct 22, 2026, 9:32:08โ€ฏAM ![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-22-2026-07-30-18-6643-AM.jpeg) A video aspect ratio is the proportion between a frame's displayed width and its displayed height, written as width:height. Three ratios dominate streaming and social video in 2026: 16:9 (1920ร—1080, 1.78:1) for TV, desktop and connected-TV players, 9:16 (1080ร—1920, 0.5625:1) for phone-first vertical feeds, and 1:1 (1080ร—1080) for square feed posts. As of 2026, a 16:9 video letterboxed on a full-screen 9:16 phone display uses only 31.6 percent of the screen (81/256). A 16:9 source burned into a 1080ร—1920 vertical frame keeps just 1080ร—608 active pixels, about 32 percent of the frame's pixel budget. Picking the wrong aspect ratio for video costs both screen area and encoded resolution. ## **How a video aspect ratio is computed: storage, pixel and display ratios** Three ratios interact in every encoded file. The storage aspect ratio is the coded width divided by the coded height. The pixel aspect ratio (PAR, which some encoders call sample aspect ratio) describes the shape of each pixel. The display aspect ratio (DAR) is what the viewer sees: DAR equals storage width over height multiplied by PAR. With square pixels (PAR 1:1), storage and display ratios are identical, which is the normal case for modern web and OTT encodes. Anamorphic sources are where the math matters. HDV stores 1440ร—1080 with a PAR of 4:3, so 1.333 ร— 1.333 gives a 16:9 display. NTSC DVD stores 720ร—480 with a PAR of 32:27, and 1.5 ร— 1.185 also lands on 1.78:1. The ratio is signalled in several places, and players disagree about which one wins. H.264 and HEVC carry PAR in the VUI section of the sequence parameter set. MP4 carries it in the pixel aspect box and the track header dimensions. HLS (RFC 8216) declares the RESOLUTION attribute on each variant stream as width ร— height, and DASH exposes width, height, sar and par attributes on the Representation and AdaptationSet. When these disagree, browsers, Android players and smart TVs resolve the conflict differently, which is the root of most "stretched on one device only" bugs. ## **Where aspect ratio sits in the streaming stack** Aspect ratio is decided at three layers. The encoder fixes the coded frame and PAR. The packager writes RESOLUTION or width and height into the manifest. The player sizes its viewport and chooses a fit mode. Only the first layer touches pixels; the other two are metadata and layout. Player sizing usually comes down to two choices. Contain mode scales the video until one dimension fills the viewport and leaves bars on the other (letterboxing for top and bottom bars, pillarboxing for side bars). Cover mode scales until both dimensions fill and crops the overflow. On the web, the CSS aspect-ratio property reserves the player box before the first segment arrives, which prevents layout shift when the manifest finally reports dimensions. ### Screen utilization matrix for common ratios | Source ratio | On a 16:9 screen | On a 9:16 screen | On a 1:1 viewport | | --- | --- | --- | --- | | 16:9 | 100 percent | 31.6 percent | 56.3 percent | | 9:16 | 31.6 percent | 100 percent | 56.3 percent | | 1:1 | 56.3 percent | 56.3 percent | 100 percent | | 4:5 | 45.0 percent | 70.3 percent | 80.0 percent | | 2.39:1 (scope) | 74.4 percent | 13.8 percent | 41.8 percent | Square 1:1 is the only ratio that never drops below 56 percent on any common screen, which is why it survives as the hedge format for feeds that serve both orientations. ## **16:9 aspect ratio vs. its neighbors: terms that get confused** Aspect ratio vs. resolution: resolution is a pixel count, aspect ratio is a shape. 1280ร—720, 1920ร—1080 and 3840ร—2160 all share the 16:9 aspect ratio, and 1080ร—1920 has exactly the same 2,073,600 pixels as 1920ร—1080 while being a completely different ratio. Display aspect ratio vs. pixel aspect ratio: DAR is the shape on screen, PAR is the shape of one stored pixel. A file can report 1440ร—1080 and still be 16:9 because its pixels are 4:3 wide; strip the PAR flag during a remux and the same file displays at 4:3, squeezed. Letterboxing vs. cropping: letterboxing preserves the full picture and spends screen area on bars, while cropping (center crop or a tracked reframe) fills the screen and discards content. Burned-in letterboxing is the worst variant, because the bars consume coded resolution in every rendition of the ladder. ## **How to encode vertical 9:16 video correctly** Encode vertical content as a native 1080ร—1920 frame with square pixels, and do not rely on rotation metadata. Phones often record a 1920ร—1080 frame plus a display matrix that says "rotate 90 degrees"; some players honor it, some ignore it, and the result is sideways playback. Bake the rotation into the pixels during transcoding and clear the rotation flag. For ffmpeg-based pipelines, the pattern is a scale filter targeting 1080 by 1920 with the original aspect ratio forced to decrease, followed by a pad filter that centers the result on a 1080 by 1920 canvas, then a setsar filter set to 1. When the source is 16:9 and the target is a vertical feed, swap pad for a crop to a 9:16 window, ideally driven by subject tracking rather than a fixed center. Keep every dimension even, since 4:2:0 chroma subsampling requires it. ### A vertical bitrate ladder | Rendition | HLS RESOLUTION value | Pixels per frame | Typical H.264 bitrate (estimate) | | --- | --- | --- | --- | | 1080p vertical | 1080x1920 | 2,073,600 | 4 to 6 Mbps | | 720p vertical | 720x1280 | 921,600 | 2 to 3 Mbps | | 540p vertical | 540x960 | 518,400 | 1 to 1.5 Mbps | | 360p vertical | 360x640 | 230,400 | 0.4 to 0.7 Mbps | Because a 9:16 rendition has the same pixel count as its 16:9 counterpart, the existing horizontal ladder's bitrates transfer directly; only the RESOLUTION value must list width first. Thumbnails and poster frames need the same treatment as the video. BlazingCDN's [**on-the-fly image processing for video posters**](https://blazingcdn.com/image-processing/) supports crop, resize, resizefit and resizefill at no extra charge, so one master poster can be served as 16:9, 1:1 and 9:16 variants without storing three copies. ## **Common aspect ratio misconceptions** - **"Vertical video needs a higher bitrate."** It does not. 1080ร—1920 and 1920ร—1080 carry identical pixel counts, so encoder complexity per frame is comparable for comparable content. - **"Letterbox bars are free because they compress to nothing."** The bars cost few bits, but they cost resolution: burned-in bars shrink the active picture in every rendition, and adaptive players cannot recover it. - **"The manifest RESOLUTION controls display."** It is a hint for variant selection. Display shape comes from the decoded frame and PAR, and a wrong RESOLUTION mostly breaks ABR selection logic. - **"Rotation metadata is a safe shortcut."** Support varies across browsers, TV platforms and older Android builds; pixels you rotate at encode time play correctly everywhere. ## **FAQ: video aspect ratio questions** ### What is the best aspect ratio for video on social platforms? For phone-first short-form feeds, 9:16 at 1080ร—1920 is the best video aspect ratio because it fills the full screen. Feed posts that appear inline in scrolling timelines often perform better at 4:5 or 1:1, which use 70 to 80 percent of a portrait screen while still fitting comfortably on desktop layouts without heavy pillarboxing. ### Is 1920x1080 always a 16:9 aspect ratio? A 1920ร—1080 frame is 16:9 only when its pixel aspect ratio is 1:1, which covers nearly all modern web and OTT encodes. If the file signals non-square pixels, the display aspect ratio changes accordingly. Always check the pixel aspect flag in the bitstream and container rather than trusting the coded dimensions alone when diagnosing stretched playback. ### How do I convert 16:9 video to 9:16 without black bars? Converting 16:9 video to 9:16 without black bars requires cropping a vertical window from the horizontal frame. A fixed center crop keeps only 31.6 percent of the original area, so speakers or action near the edges get cut. Subject-tracked reframing moves the crop window per shot and is the standard approach for repurposing horizontal footage at scale. ### Should I declare vertical video resolution as 1080x1920 in HLS manifests? Yes, an HLS manifest should declare vertical video resolution as 1080x1920, because RFC 8216 defines RESOLUTION as width followed by height. Writing 1920x1080 for a vertical rendition misleads player variant selection, which compares declared dimensions against viewport size, and can cause the player to choose a rendition that is too large or too small. ## **Audit your aspect ratio pipeline this week** Pull a sample of 50 recent vertical uploads and inspect each with ffprobe: compare coded width and height, the sample aspect ratio, any rotation side data, and the RESOLUTION value your packager wrote into the HLS master playlist. Any file where rotation metadata is present, PAR is not 1:1, or RESOLUTION lists height first is a playback bug waiting on a specific device. Fix it at encode time, then re-test on one iOS, one Android and one smart TV player. If your vertical and horizontal libraries are growing, the [**BlazingCDN Video CDN for HLS and DASH libraries**](https://blazingcdn.com/video-cdn/) replicates pre-encoded renditions inside the CDN and keeps your origin out of the delivery path. Share: [f](https://www.facebook.com/sharer/sharer.php?u=https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1) [in](https://www.linkedin.com/sharing/share-offsite/?url=https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1) [๐•](https://twitter.com/intent/tweet?url=https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1&text=) [โœ‰](mailto:?subject=%3Cspan%20id="hs_cos_wrapper_name"%20class="hs_cos_wrapper%20hs_cos_wrapper_meta_field%20hs_cos_wrapper_type_text"%20style=""%20data-hs-cos-general-type="meta_field"%20data-hs-cos-type="text"%20%3EVideo%20Aspect%20Ratios%20Explained:%2016:9,%209:16%20and%201:1%3C/span%3E&body=https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1) ![BlazingCDN](https://blog.blazingcdn.com/hs-fs/hubfs/Logo/blog-logo-w.png?height=24&name=blog-logo-w.png) *Heavy traffic.* Light bill. The CDN for video and large traffic Their monthly bill vs ours - 20 TBFastly $2,087**$92.50** - 50 TBCDN77 $990**$215** - 200 TBCloudFront $11,965**$765** Published list prices, Aug 2026 [Calculate your cost](https://blazingcdn.com/cdn-cost-calculator/?utm_source=blog&utm_medium=sidebar&utm_campaign=blog_sidebar&utm_content=compare_calc) ## Related posts [![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-22-2026-07-00-44-8612-AM.jpeg)](https://blog.blazingcdn.com/en-us/cloud-video-platform-and-cloud-video-streaming-a-guide-for-modern-media-2024?hsLang=en-us) Learn ### [Cloud Video Streaming Platforms: How They Work and What to Choose](https://blog.blazingcdn.com/en-us/cloud-video-platform-and-cloud-video-streaming-a-guide-for-modern-media-2024?hsLang=en-us) Cloud video streaming moves video through four managed stages: ingest, transcoding into an adaptive bitrate ladder, ... Oct 22, 2026, 9:02:53โ€ฏAM [Read more](https://blog.blazingcdn.com/en-us/cloud-video-platform-and-cloud-video-streaming-a-guide-for-modern-media-2024?hsLang=en-us) [![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Oct-21-2026-07-30-22-5336-AM.jpeg)](https://blog.blazingcdn.com/en-us/4k-streaming-bandwidth-how-much-speed-and-data-you-need?hsLang=en-us) Video - Video & Streaming ### [4K Streaming Bandwidth: How Much Speed and Data You Need](https://blog.blazingcdn.com/en-us/4k-streaming-bandwidth-how-much-speed-and-data-you-need?hsLang=en-us) 4K streaming bandwidth comes down to codec and frame rate. As of 2026, a 4K stream in HEVC at 24 or 30 fps typically ... Oct 21, 2026, 9:32:41โ€ฏAM [Read more](https://blog.blazingcdn.com/en-us/4k-streaming-bandwidth-how-much-speed-and-data-you-need?hsLang=en-us) [![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us) [๐Ÿ“˜ Learn](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [๐Ÿ“Š Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [๐ŸŽฌ Video & Streaming](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [๐Ÿญ Industries](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [๐Ÿ’ฐ Pricing & Costs](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [โšก Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [๐Ÿ”’ Security](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [๐Ÿ› ๏ธ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [โœ๏ธ Publish with us](https://blog.blazingcdn.com/publish-with-us?hsLang=en-us) in f ๐• โœ‰ Copyright ยฉ BlazingCDN |. All rights reserved. ```json { "@context" : "https://schema.org", "@id" : "https://blazingcdn.com/#organization", "@type" : "Organization", "description" : "High-volume CDN for video, live streaming, OTT/IPTV, software, games, SaaS and large-file delivery.", "logo" : { "@id" : "https://blazingcdn.com/#logo", "@type" : "ImageObject", "height" : 560, "url" : "https://blazingcdn.com/wp-content/uploads/2024/08/logo-560-560.png", "width" : 560 }, "name" : "BlazingCDN", "sameAs" : [ "https://www.linkedin.com/company/blazingcdn", "https://x.com/BlazingCdn", "https://www.reddit.com/r/BlazingCDN/", "https://www.wikidata.org/wiki/Q141711074" ], "url" : "https://blazingcdn.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/#website", "@type" : "WebSite", "inLanguage" : "en-US", "name" : "BlazingCDN Blog", "publisher" : { "@id" : "https://blazingcdn.com/#organization" }, "url" : "https://blog.blazingcdn.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1#article", "@type" : "BlogPosting", "author" : { "@id" : "https://blog.blazingcdn.com/en-us/author/blazingcdn#person", "@type" : "Person", "description" : "Vadym Borovskyi is Chief Product and Marketing Officer at BlazingCDN, where he has led product strategy and growth since 2021. He has more than 11 years of experience in IT product management and B2B marketing. On this blog he writes about CDN pricing and egress costs, video and software delivery, cache configuration, and how teams evaluate and switch CDN providers. He is based in Warsaw, Poland.", "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/vadym-borovskyi.jpg", "jobTitle" : "Chief Product and Marketing Officer", "knowsAbout" : [ "Content Delivery Networks (CDN)", "CDN pricing", "Video streaming delivery", "Software and game distribution", "Cache optimization", "Product Management", "B2B Marketing", "Digital Marketing", "Pay Per Click Marketing (PPC)", "Google Ads", "Search Engine Marketing (SEM)", "Marketing Strategy", "Artificial Intelligence (AI)", "Cloud Management", "SaaS Development", "IT Consulting", "Computer Networking", "Project Management", "Startups" ], "name" : "Vadym Borovskyi", "sameAs" : [ "https://www.linkedin.com/in/axelt/" ], "url" : "https://blog.blazingcdn.com/en-us/author/blazingcdn", "worksFor" : { "@id" : "https://blazingcdn.com/#organization" } }, "dateModified" : "2026-10-22T07:32:08Z", "datePublished" : "2026-10-22T07:32:08Z", "description" : "Explore video aspect ratio basics, including 16:9 aspect ratio, 9:16, and 1:1, and find the best aspect ratio for video on any platform.", "headline" : "Video Aspect Ratios Explained: 16:9, 9:16 and 1:1", "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/Gemini-Blog/image-Oct-22-2026-07-30-18-6643-AM.jpeg", "inLanguage" : "en-us", "isPartOf" : { "@id" : "https://blog.blazingcdn.com/#website" }, "mainEntityOfPage" : { "@id" : "https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1", "@type" : "WebPage" }, "publisher" : { "@id" : "https://blazingcdn.com/#organization" }, "wordCount" : 1589 } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1#breadcrumb", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://blog.blazingcdn.com/en-us", "name" : "Blog", "position" : 1 }, { "@type" : "ListItem", "item" : "https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1", "name" : "Video Aspect Ratios Explained: 16:9, 9:16 and 1:1", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.blazingcdn.com/en-us/video-aspect-ratios-explained-16-9-9-16-and-1-1#faq", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "For phone-first short-form feeds, 9:16 at 1080ร—1920 is the best video aspect ratio because it fills the full screen. Feed posts that appear inline in scrolling timelines often perform better at 4:5 or 1:1, which use 70 to 80 percent of a portrait screen while still fitting comfortably on desktop layouts without heavy pillarboxing." }, "name" : "What is the best aspect ratio for video on social platforms?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "A 1920ร—1080 frame is 16:9 only when its pixel aspect ratio is 1:1, which covers nearly all modern web and OTT encodes. If the file signals non-square pixels, the display aspect ratio changes accordingly. Always check the pixel aspect flag in the bitstream and container rather than trusting the coded dimensions alone when diagnosing stretched playback." }, "name" : "Is 1920x1080 always a 16:9 aspect ratio?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Converting 16:9 video to 9:16 without black bars requires cropping a vertical window from the horizontal frame. A fixed center crop keeps only 31.6 percent of the original area, so speakers or action near the edges get cut. Subject-tracked reframing moves the crop window per shot and is the standard approach for repurposing horizontal footage at scale." }, "name" : "How do I convert 16:9 video to 9:16 without black bars?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes, an HLS manifest should declare vertical video resolution as 1080x1920, because RFC 8216 defines RESOLUTION as width followed by height. Writing 1920x1080 for a vertical rendition misleads player variant selection, which compares declared dimensions against viewport size, and can cause the player to choose a rendition that is too large or too small." }, "name" : "Should I declare vertical video resolution as 1080x1920 in HLS manifests?" } ] } ```