ForHosting KIT · Developer Utilities

Standard resolutions for an aspect ratio

Choosing dimensions is easier when you can start from formats that displays, video tools, presentation software, and publishing platforms already recognize.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

This aspect ratio resolution lookup takes one supported ratio—16:9, 4:3, 21:9, or 1:1—and returns a practical list of common resolutions. Every result includes width, height, a familiar label, and total pixel count, making it useful for planning exports, comparing workloads, or configuring repeatable media pipelines without searching several reference tables.

Choose the ratio that describes your canvas

An aspect ratio expresses the relationship between width and height, not the absolute size of an image or screen. A 16:9 canvas is wider than it is tall and is the familiar choice for modern video, presentations, and televisions. The older 4:3 shape remains common in archival video, projectors, embedded displays, and some document layouts. A 21:9 selection covers the standard resolutions commonly marketed as ultrawide, while 1:1 provides square canvases frequently used for artwork, thumbnails, and social publishing. Enter the ratio exactly as one of the supported values. The result is a curated set of useful dimensions rather than every mathematical multiple of that ratio. That distinction keeps the list practical: technically, infinitely many width and height pairs can share a proportion, but only a smaller set is routinely recognized by software, devices, or production teams. If the ratio is outside the supported set, the lookup returns a clear input error instead of guessing or silently substituting a nearby format.

Read each resolution record

Each returned record includes numeric width and height values, a compact resolution string, a familiar format label, and the total number of pixels. Width and height are the values to copy into an encoder, design tool, rendering command, or application configuration. The label helps people recognize standards such as Full HD, QHD, VGA, or UltraWide QHD without having to memorize their dimensions. Pixel count is included because two canvases with the same shape can require very different amounts of processing, memory, storage, and network bandwidth. For example, moving to twice the width and twice the height creates four times as many pixels. The records are ordered from smaller to larger dimensions, so they can be used directly in a size selector or scanned as a progression of increasing detail. Some marketed formats, especially ultrawide formats and 854 by 480 video, are conventional approximations of the named display ratio due to integer pixel dimensions. The lookup preserves those widely used standards instead of inventing impractical fractional pixels.

Use the lookup in production decisions

The list is useful wherever a workflow needs sensible presets but should not hard-code unexplained numbers. A video service can offer recognized export sizes for a selected canvas shape. A design system can populate a preset menu while retaining width and height as machine-readable integers. A capacity-planning script can compare pixel counts before selecting a render target, helping prevent an accidental 8K job when Full HD is sufficient. The response is deterministic: the same supported ratio always returns the same ordered records, with no network request, randomness, or time-dependent data. That makes it safe for tests, build tools, configuration generators, and reproducible automation. Treat these entries as common starting points rather than a claim that other dimensions are invalid. Custom dimensions can still preserve a ratio, and delivery platforms may impose their own codec, file-size, or maximum-dimension rules. This capability answers the narrower question of which conventional resolutions commonly correspond to a chosen ratio, leaving cropping, scaling, bitrate selection, and platform compliance to the appropriate tools in your workflow.

Build an export preset menu

Populate a video or image export control with familiar dimensions after the user selects a supported aspect ratio.

Estimate rendering workload

Compare the returned pixel counts before choosing between HD, QHD, 4K, or another standard output size.

Standardize media configurations

Generate consistent width and height settings for tests, templates, encoders, and repeatable publishing pipelines.

Which aspect ratios are supported?

The supported values are 16:9, 4:3, 21:9, and 1:1. Any other value returns an invalid input error.

Does the list include every possible matching dimension?

No. There are infinitely many proportional dimensions, so the response focuses on common named or widely used standards.

Why are some ultrawide dimensions not mathematically exact 21:9?

The display industry commonly groups several nearby integer-pixel formats under the 21:9 marketing label. The lookup reports those established formats.

What does pixels mean in the response?

It is width multiplied by height. It provides a quick way to compare the processing and storage scale of different resolutions.

Does this tool resize an image or video?

No. It returns reference dimensions only; it does not upload, crop, scale, encode, or modify media.

What does the API request cost?

Each API request costs $0.002. The browser version can run locally without a server-side lookup.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/misc2/aspect-ratio-resolution-lookup

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/misc2/aspect-ratio-resolution-lookup \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ratio":"16:9"}'
{
  "ratio": "16:9"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "misc2.aspect_ratio_resolution_lookup",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →