What is 640x480?

640x480 is a frame containing 640 horizontal pixels and 480 vertical pixels, producing a 4:3 aspect ratio. It is historically associated with VGA displays and video.

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 640x480.

How 640x480 works

The 640×480 raster is a specific sample grid whose square-pixel presentation forms a 4:3 picture. Its association with VGA is historical, but dimensions alone do not define a display timing, refresh rate, color depth, codec, or transport. In contemporary media systems it usually appears during legacy ingest, low-resolution capture, compatibility testing, or delivery to equipment with fixed raster requirements.

Key facts

  1. With square pixels, 640 divided by 480 reduces exactly to 4:3; non-square pixel metadata could still instruct a player to display the stored raster differently.
  2. “VGA” describes more than dimensions in its original display context, so a 640×480 video file is not automatically an encoded VGA signal or VGA-compatible transport.
  3. Stretching this raster directly to a 16:9 canvas changes horizontal proportions; preserving geometry requires side padding or cropping from the top and bottom.

When 640x480 matters

Preserve 640x480 when a legacy camera, archive, or conferencing system requires the native frame. Scaling it to widescreen without cropping or padding will stretch the image.

Common use cases for video

These examples cover video broadly, not specifically 640x480.

  • 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 640x480.

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