Screen size converter

Diagonal units, aspect ratios, and how width and height are derived

Send it as the required field diagonal (aliases size, d, and diagonal_size are accepted) together with unit set to in or inch when the number is imperial, or cm when it is metric. Both parts must be positive finite numbers; zero, negative, empty, or non-numeric parts are rejected as invalid aspect ratio with invalid_input so furniture and CAD tools never receive a nonsense panel. Internally the engine converts the diagonal to inches, divides by the Euclidean norm of the aspect pair, and multiplies back by each component: width equals aspect_w times diagonal over the square root of aspect_w squared plus aspect_h squared, and height uses aspect_h the same way. Identical inputs always produce identical JSON because the path is pure arithmetic with no network, no random seed, and no wall clock.

Reading the dimensions response and choosing common ratios

Common living-room and desktop ratios include 16:9 for HDTV and most monitors, 4:3 for older sets and some medical or industrial panels, 21:9 and 32:9 for ultrawide gaming and productivity displays, and 16:10 for many laptop and professional screens. If a listing omits the ratio, assume 16:9 for modern consumer TVs but confirm for specialty or vintage gear. On success the response echoes the input diagonal and unit, then diagonal_in and diagonal_cm so you always see both systems even when you only supplied one. Fields aspect_ratio, aspect_w, and aspect_h restate the normalized ratio label used for the calculation. The practical fit numbers are width_in, height_in, width_cm, and height_cm: those are the active-panel extents under the ideal rectangle model, not cabinet depth or bezel thickness. Area_in2 and area_cm2 multiply width by height for rough comparisons of how much glass you get at a given diagonal. The formula string restates the Pythagoras scaling and the SI conversion factor for transparency in audit logs, and method is always tv_size_pythagoras so downstream code can branch without sniffing shapes. Missing diagonal, non-positive diagonal, unknown units, and invalid aspect ratios all fail with invalid_input and are not charged after the engine rejects the request.

API usage, pricing, fit workflows, and practical limits

Call the free in-browser screen size converter for shopping comparisons, wall-mount planning, and classroom demos of Pythagoras without installing a spreadsheet. Remember that marketed diagonals refer to the viewable panel, not the outer plastic or metal frame, so leave a small clearance for bezels and ventilation when checking a niche. Authors shipping SDKs can map width and height fields directly into tables that show inches and centimetres side by side—the same dual units shoppers expect when comparing global listings. Send a JSON body with the required positive diagonal, optional unit defaulting to inches, and a required aspect_ratio string such as 16:9. Use the prepaid API when a retailer product page, home-theatre configurator, logistics packing estimator, or furniture marketplace needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with general unit converters when you also need depth or stand dimensions, or with image tools when you are generating mockups at the correct physical proportions.