What is 360p?

360p denotes progressive video with 360 vertical pixels. For 16:9 content it is commonly encoded at 640x360, although the horizontal dimension can vary with aspect ratio.

Video + audio tracks
Playable derivative
Video processing decodes timed tracks, transforms them, and encodes a deliverable for a target player. This diagram shows video broadly, not specifically 360p.

How 360p works

The 360p label identifies vertical sampling and progressive presentation, not a unique width, frame rate, bitrate, or codec. A 16:9 rendition normally uses 640 horizontal samples, while differently shaped content can retain another width. Within a delivery ladder, this tier trades spatial detail for lower transfer and decode demands, making preprocessing choices such as scaling filters and text legibility especially consequential.

Key facts

  1. The “p” means complete frames are presented progressively rather than divided into interlaced fields; it does not identify frames per second.
  2. A 640×360 raster is exactly 16:9 with square pixels, but calling any asset 360p does not by itself prove that its pixels are square or its width is 640.
  3. Fine captions, interface captures, and thin line art can become unreadable after reduction, even when photographic scenes remain recognizable at the same resolution.

When 360p matters

Include a 360p rendition as a fallback for constrained mobile networks or small displays. Its lower data demand reduces buffering, but text and fine detail may become difficult to resolve.

Common use cases for video

These examples cover video broadly, not specifically 360p.

  • Preparing uploaded video for web, mobile, connected-TV, social, or editorial playback.
  • Creating clips, thumbnails, captions, alternate aspect ratios, and adaptive renditions.
  • Normalizing camera, screen-recording, and user-generated files into predictable outputs.

Working with video

This guidance covers video broadly, not just 360p.

A demuxer separates tracks from the container, decoders turn compressed streams into frames or samples, and filters apply spatial or temporal changes. Encoders compress the transformed tracks before a muxer writes the chosen output container.

Video compatibility is the product of codec, container, profile, level, frame rate, color, audio, and subtitles. Validate the complete output on target devices because a playable file on one decoder may fail or look different on another.

What you gain

  • Standardized derivatives make diverse source files playable on target devices.
  • A retained master can feed many resolutions, aspect ratios, codecs, and channels.
  • Automated inspection and transformation make large upload volumes consistent.

What it costs

  • More efficient codecs can lower bitrate at similar quality but usually cost more compute and may have narrower support.
  • Higher resolutions and frame rates preserve more detail and motion while increasing processing and delivery requirements.
  • Fast encoding settings improve throughput but can produce larger files or lower quality than slower analysis.

Before production

  1. Inspect codec, container, dimensions, frame rate, color, audio, and subtitle tracks.
  2. Test visual quality and playback support across the slowest and oldest target devices.
  3. Preserve a suitable master before applying lossy, destructive, or delivery-specific changes.

Turn media knowledge into a working pipeline

Connect uploads, processing, AI, storage, and delivery through one declarative API — with the encoding stack, scaling, and format churn handled for you.

Try Transloadit for free