If you are searching for how to translate screen resolution, how to translate aspect ratio and refresh rate, or how to preserve pixel density, display size and monitor specifications across languages, the first rule is that these numbers describe different properties. A value such as 1920×1080 describes a pixel matrix, 16:9 describes a proportion, 120 Hz describes update frequency, and 326 ppi describes pixel density. They should never be merged or casually converted into one another.
Display-specification translation matters in monitor listings, television specifications, smartphones, tablets, laptops, gaming displays, projectors, digital signage, product manuals and e-commerce pages. A target-language description can sound fluent while becoming technically wrong if width and height are reversed, refresh rate is mistaken for frame rate, diagonal size is treated as panel width, or ppi is translated as total pixels.
This guide explains how to translate screen resolution, aspect ratio, refresh rate, pixel density and related display specifications without changing the device. It covers pixel dimensions, native resolution, ultrawide formats, portrait orientation, Hz, variable refresh rate, ppi, dpi, diagonal screen size, scaling, colour depth, HDR labels, response time and how to verify the final translation against manufacturer data and the actual display mode.
Why display specifications are easy to confuse
Display specifications describe several independent dimensions of a screen. Resolution tells us how many addressable pixels are arranged horizontally and vertically. Aspect ratio tells us the relationship between width and height. Refresh rate tells us how frequently the panel can refresh an image. Pixel density describes how tightly pixels are packed into a physical area. A screen can therefore have the same resolution as another screen but a different physical size and a different pixel density.
Marketing language makes the problem harder. Terms such as Full HD, QHD, 4K, UHD, Retina, high refresh rate, adaptive sync and gaming display may sit beside exact numeric specifications. Some are formal standards, some are broad market labels, and some are manufacturer branding. Translation should preserve exact numeric data and treat the descriptive label according to how the manufacturer actually uses it.
Orientation creates another source of error. A 1080×1920 portrait display contains the same total number of pixels as a 1920×1080 landscape display, but the width-height order is reversed. If a translator normalizes every resolution into the more familiar landscape order, the target text can describe the wrong orientation.
The safest principle is to protect the technical values first, identify what property each value represents, then translate the surrounding labels and explanation. When a conversion or reformatting is requested, verify that the underlying display still represents the same pixel matrix, ratio, physical size and performance class.
A reliable translation method
1. Classify every number before translating
Mark each value as resolution, diagonal size, aspect ratio, refresh rate, response time, pixel density, brightness, contrast, colour depth or another display property. This prevents one number from being attached to the wrong label during sentence reordering.
2. Preserve width-height order
Keep the source orientation unless the product specification explicitly uses another convention. When the target language naturally places labels in a different order, make the width and height labels explicit rather than moving the numbers by habit.
3. Separate exact specifications from marketing names
Terms such as Full HD or 4K can be useful search language, but the exact pixel dimensions are the strongest technical anchor. Preserve the manufacturer’s terminology without letting the marketing label replace a more precise specification.
4. Keep refresh rate distinct from frame rate
A panel refresh rate in hertz is a display capability. Frames per second describe content or rendering output. They interact, but they are not the same metric. Translate each according to its technical role.
5. Keep ppi, dpi and pixel count distinct
Pixels per inch commonly describes display pixel density, while dots per inch can refer to printing or device output. Neither is the same as total pixel resolution. Preserve the source abbreviation and explain it only when useful.
6. Preserve native-versus-supported modes
A monitor may accept many input resolutions but have one native panel resolution. Translate the distinction clearly so the target reader does not assume every supported mode has the same physical sharpness.
7. Protect technical symbols and units
Keep Hz, ms, ppi, nits, bit-depth notation, multiplication signs and ratio punctuation consistent. If local typography changes the symbol style, verify that the technical relationship remains obvious.
8. Verify against the actual device or manufacturer sheet
Check the official display specification, operating-system display mode or product manual. Retail listings can contain mistakes, and translation should not amplify a bad secondary source.
Twenty-four recurring display-translation problems
1. 1920×1080 resolution
A source entry such as 1920×1080 describes 1,920 horizontal pixels by 1,080 vertical pixels in a typical landscape orientation. Do not translate the multiplication sign as a mathematical operation producing a single number, and do not reverse the values because another style guide prefers height before width. The relationship between the two dimensions matters.
The safest target wording keeps the exact matrix and, where useful, adds a label such as “resolution” or “pixel resolution.” If the article also uses Full HD, make sure the marketing label refers to the same mode rather than becoming a replacement for the numbers.
For QA, compare the target string with the manufacturer sheet and the operating-system display mode. If the target version says 1080×1920 while the product is being described in landscape, the translation has changed orientation.
2. 2560×1440 and QHD terminology
A QHD-class display is often presented as 2560×1440. Preserve the exact pixel matrix and treat QHD as a product-category label rather than translating it into an unrelated phrase such as “high definition.” Generic adjectives lose the distinction between 1080p, 1440p and other modes.
If the source says “QHD 2560×1440,” translate the descriptive part but keep QHD and the resolution traceable. Where a local market uses another familiar label, it can be added only if it does not create ambiguity about the actual pixel count.
QA should check that the numbers remain in the same order, that no zero is dropped, and that the QHD label remains paired with the correct product variant.
3. UHD and 4K wording
Consumer displays commonly use “4K” beside UHD specifications such as 3840×2160. The two labels can be used loosely in marketing, while cinema and professional contexts may use different 4K pixel dimensions. Translation should therefore preserve the source wording and exact resolution instead of assuming every occurrence of “4K” means one universal matrix.
When the source includes both “4K UHD” and the numeric resolution, keep both layers. The marketing phrase helps users search and recognize the product class; the numbers anchor the technical meaning.
For QA, verify the display’s native resolution. If the target text calls a product 4K without the same manufacturer evidence as the source, the translation has added a claim.
4. Ultrawide resolutions
Ultrawide displays may use resolutions such as 3440×1440 or 5120×1440. These should not be shortened to ordinary “1440p” without preserving the much wider horizontal dimension. The width is what distinguishes the product from a conventional 16:9 display with the same vertical pixel count.
Translate ultrawide or super-ultrawide terminology as product descriptors, but keep the exact matrix and aspect ratio if supplied. Do not infer an aspect ratio solely from a marketing name when the numeric specification is available.
QA should compare resolution, ratio and physical size together. A 5120×1440 product is not equivalent to a 2560×1440 monitor merely because both end in 1440.
5. Portrait-mode resolution
A digital-signage panel or mobile interface may list 1080×1920 because it is intentionally portrait-oriented. Translators often normalize the pair to 1920×1080 out of familiarity, but that silently changes the intended orientation.
Keep the source order, and translate “portrait” or “vertical” according to the target-language convention. If a design document needs both orientations, label each one explicitly rather than relying on the reader to infer the axis order.
For QA, compare the target to the actual installation drawing or content canvas. A vertical signage screen should still be described as vertical after translation.
6. 16:9 aspect ratio
The ratio 16:9 expresses proportional width to height. It is not a resolution and does not state a physical size. Many resolutions can share the same aspect ratio. Translating it as if it meant “widescreen resolution” loses the distinction between geometry and pixel count.
Keep the colon and values exact. Translate “aspect ratio” with the accepted technical term and, if useful, explain that the ratio describes shape rather than the number of pixels.
QA can compare two different 16:9 modes, such as 1920×1080 and 3840×2160, to confirm the target text does not imply that one ratio corresponds to only one resolution.
7. 21:9 and ultrawide ratios
Marketing may describe an ultrawide display as 21:9 even when the exact mathematical relationship differs slightly depending on the pixel matrix. Translation should preserve the manufacturer’s ratio label rather than recalculating and “correcting” it inside ordinary product copy.
If the document is technical rather than promotional, the exact resolution can be included beside the ratio so users can see the underlying geometry. Do not replace the ratio with a translated adjective such as “very wide.”
QA should maintain consistency across title, specification table and body copy so one section does not call the same display 21:9 and another accidentally state 16:9.
8. 60 Hz refresh rate
A refresh rate of 60 Hz means the display can refresh sixty times per second under the stated mode. Translate the label, keep the number and unit exact, and do not rewrite the value as 60 frames per second unless the source specifically discusses frame rate.
Hz is a frequency unit. It should remain recognizable in the target text, even if local typography inserts a space between number and unit. The technical relationship matters more than stylistic variation.
For QA, compare the translated specification against the display mode. If the device supports 60 Hz only at some resolutions, keep the mode conditions attached.
9. 120 Hz, 144 Hz and gaming displays
High-refresh gaming monitors commonly advertise 120 Hz, 144 Hz, 165 Hz, 240 Hz or more. These values are product specifications, not adjectives. Translating “high refresh rate” without preserving the exact Hz number can hide an important difference between models.
Keep the numerical mode and any overclock or maximum conditions. If the source distinguishes “native 165 Hz” from “overclocked 180 Hz,” the target must keep that distinction rather than presenting both as ordinary supported rates.
QA should verify the cable, resolution or input conditions when they appear in the source specification, because maximum refresh rate can depend on the connection mode.
10. Variable refresh rate
Variable refresh rate, adaptive sync and vendor-branded synchronization technologies describe behavior rather than one fixed Hz value. Translate the generic concept naturally while preserving trademarked or manufacturer-specific names exactly.
If a source gives a range such as 48–144 Hz, keep the endpoints and dash relationship exact. The range is operational information, not merely marketing copy.
For QA, confirm that the target text does not turn an adaptive range into a fixed maximum or imply compatibility with a branded standard that the source did not claim.
11. Pixel density in ppi
A display density such as 326 ppi means approximately 326 pixels per inch along a linear dimension under the stated calculation. It does not mean the screen has only 326 pixels, and it is not the same as diagonal size.
Keep ppi or the established target term “pixels per inch” when explanatory text is required. Do not substitute dpi simply because a local style guide is more familiar with printing terminology.
QA can check the stated ppi against resolution and physical size if needed. A major mismatch can reveal that the source or translation attached the value to the wrong display variant.
12. DPI versus PPI
DPI and PPI are often used loosely in consumer language, but technical content may distinguish printer dots from display pixels. Translation should follow the source discipline rather than collapsing both into one generic “resolution” term.
If the source says ppi for a panel, preserve it. If documentation uses dpi for a touchscreen coordinate or print output setting, translate the surrounding context without silently standardizing the abbreviation.
QA should trace each occurrence to its object: screen, printer, image metadata or interface scaling. That context determines whether the unit is being used technically or colloquially.
13. Diagonal screen size
A “27-inch monitor” normally refers to diagonal display size, not width. Translators should preserve the diagonal concept and avoid presenting 27 inches as horizontal width when explaining the specification.
When metric equivalents are required, convert the diagonal separately and label the converted value clearly. Do not derive width or height from diagonal size unless aspect ratio and calculation are explicitly part of the task.
QA should compare the target to the official panel size and note whether the manufacturer measures the visible area or nominal class size.
14. Native resolution
Native resolution identifies the panel’s physical pixel grid. A monitor may accept lower or different input resolutions, but scaling them does not change the native matrix. Translate “native” distinctly from “supported,” “maximum input” or “recommended.”
Preserve the exact native mode and any conditions. If the source says “native 3840×2160; supports 1920×1080,” the target should retain both relationships rather than listing two apparently equal resolutions.
For QA, use the product manual or display settings to confirm which mode is native.
15. Scaling and logical resolution
Operating systems can render interfaces at a logical scale different from the physical pixel grid. A high-density laptop may have a 2880×1800 panel while using a scaled desktop that appears as a lower logical workspace. Translation should keep panel resolution and UI scaling separate.
Terms such as 125%, 150% or 200% scaling refer to interface presentation. Do not translate them as reduced physical resolution unless the source explicitly says the output mode changes.
QA should compare the operating-system setting and hardware specification so the target article does not imply that scaling alters the actual number of panel pixels.
16. Response time in milliseconds
Response time values such as 1 ms or 5 ms describe pixel transition behavior under a specified measurement method. They are not refresh rates. Translate the label and keep the millisecond unit exact.
If the source distinguishes grey-to-grey, moving-picture response time or another method, preserve the method label. A bare “1 ms” claim can mean different things across manufacturers.
QA should ensure response time remains in milliseconds and is not accidentally attached to input lag or refresh rate in the target table.
17. Brightness in nits or cd/m²
Display brightness may be expressed in nits or candela per square metre. Translate the brightness label while preserving the source unit and distinction between typical, peak and sustained values.
Do not convert a peak HDR brightness claim into ordinary full-screen brightness unless the source does so. These conditions can describe different operating states.
QA should keep “typical,” “maximum,” “peak” and test-window qualifiers attached to the right number.
18. Colour depth
Colour depth may be described as 8-bit, 10-bit or with additional processing terminology. The bit depth is not the same as the number of colours written out in marketing copy, and an “8-bit + FRC” implementation should not be simplified to native 10-bit unless the source claims that.
Preserve the numeric bit depth and qualifiers. Translate generic phrases such as “colour depth” or “panel depth” consistently across specification tables.
QA should compare the panel specification and input support because a display may accept 10-bit input without having a native 10-bit panel.
19. HDR labels
HDR may refer to a broad high-dynamic-range capability or to specific certification and format names. Preserve standardized or trademarked labels exactly, and translate explanatory text without inventing compatibility.
If the source lists several supported HDR formats, keep them as separate compatibility items. Do not reduce them to a generic “HDR supported” statement if format-level detail matters to the buyer.
QA should check the official product specification because retailer pages frequently overgeneralize HDR support.
20. Touch resolution and display resolution
A touchscreen can have a display pixel resolution and a separate touch-sensor coordinate system or sampling specification. Do not assume every “resolution” value on a touch device refers to visible pixels.
Translate the object of measurement explicitly: display resolution, touch resolution, touch sampling rate or coordinate precision. This prevents unrelated values from being merged in the target specification.
QA should trace each number to the correct subsystem in the manual or developer documentation.
21. Projector native and input resolutions
Projectors often advertise compatibility with high-resolution input while using a lower native imaging device. Translation should preserve the difference between “accepts 4K input,” “supports 4K signal” and “native 4K resolution.”
Do not convert signal support into a native-resolution claim. Keep input compatibility and physical imaging resolution in separate fields.
QA should compare the projector panel or chip resolution with the supported input table.
22. Multi-monitor combined resolution
A workstation may describe a combined desktop such as 3840×1080 across two 1920×1080 monitors. Translation should preserve whether the value refers to one panel or the aggregate workspace.
Translate “combined,” “spanned,” “extended desktop” or equivalent terms clearly. Otherwise a target reader may think each individual display has the larger resolution.
QA should count the displays and verify how the operating system arranges them.
23. Rotated digital signage
Digital signage systems can rotate content 90, 180 or 270 degrees. Translation should preserve the rotation instruction and the source coordinate orientation. Rewriting every canvas as landscape dimensions can break media templates.
Keep orientation terms, rotation angles and resolution values connected. If the system expects a portrait asset at 1080×1920, that exact canvas should remain visible in the target workflow.
QA should preview the asset in the signage player rather than assuming a text-only review is enough.
24. Specification tables with multiple display modes
A manual may list several combinations of resolution and refresh rate, such as 3840×2160 at 60 Hz and 2560×1440 at 144 Hz. Translation must preserve the row structure because each rate belongs to a particular mode.
Do not sort the values independently or collapse them into two separate lists. The pairings are part of the specification. If the target table is reformatted, keep every mode as one connected record.
For QA, compare the target table row-by-row with the source and test representative modes where practical.
Common failure modes
Reversing width and height
Resolution order can encode orientation. Preserve the source axis order unless an explicit target-format conversion is required.
Calling every resolution “4K”
Marketing labels are not substitutes for exact pixel dimensions. Keep the numeric mode visible when technical precision matters.
Confusing refresh rate and frame rate
Hz describes display refresh; fps describes rendered or encoded frames. Translate them as separate concepts.
Replacing ppi with dpi automatically
The units can serve different technical domains. Follow the source terminology and object being measured.
Dropping mode conditions
Maximum refresh or colour depth can depend on resolution, port, cable or operating mode. Keep those conditions attached.
Treating diagonal size as width
Monitor and television class sizes are generally diagonal measurements. Do not present them as horizontal width.
Merging native and supported resolution
A display can accept modes that are not its physical pixel grid. Preserve the distinction.
Proofreading only the prose
Technical tables fail when values migrate between rows. Compare every number, unit and label against the source independently.
Worked practice
Practice 1: Gaming monitor
Situation: A product lists 2560×1440, 165 Hz, 1 ms, 27 inches and 109 ppi. Reasoning: Treat each number as a separate technical property. Keep the resolution, refresh rate, response time, diagonal size and density in distinct fields, then translate the labels around them.
Practice 2: Smartphone display
Situation: A phone lists 2556×1179 pixels, a high pixel density and an adaptive refresh range. Reasoning: Preserve the exact matrix, ppi value and refresh range; do not infer width-height orientation from a desktop-monitor convention.
Practice 3: Projector
Situation: The projector accepts 4K input but has a lower native imaging resolution. Reasoning: Translate input compatibility and native resolution as separate claims so the target does not upgrade the physical panel.
Practice 4: Portrait signage
Situation: Content must be created at 1080×1920. Reasoning: Keep the portrait canvas in that order and translate the orientation instruction instead of normalizing the pair to landscape.
Practice 5: Laptop scaling
Situation: The panel is high resolution, but the operating system uses 150% UI scaling. Reasoning: Preserve the physical panel resolution and the logical scaling setting as different specifications.
Practice 6: Multi-mode specification
Situation: One table lists 4K at 60 Hz and QHD at 144 Hz. Reasoning: Translate row-by-row and never separate the resolutions from the rates they support.
Practice 7: HDR television
Situation: Several HDR format names appear beside a peak-brightness value. Reasoning: Preserve the format names, translate explanatory text, and keep peak brightness distinct from ordinary typical brightness.
Practice 8: Two-monitor workspace
Situation: The desktop spans two 1920×1080 monitors. Reasoning: Translate the combined-workspace description so 3840×1080 is not presented as the resolution of each monitor.
Manufacturer specifications, calculators and AI
Manufacturer specification sheets, operating-system display settings and product manuals are the strongest sources for display translation. Retail listings are useful for discovery but may simplify native resolution, HDR support or refresh-rate conditions.
Calculators can help verify aspect ratio or pixel density when a project explicitly requires explanation, but the source specification should remain the primary factual record. Recalculate only as a quality check unless the brief asks for a converted or derived value.
AI can explain display terminology, but it may normalize 4K labels, swap ppi and dpi, or assume landscape orientation. Protect exact specifications in prompts and verify every technical number independently before publication.
How this fits the wider eduKate translation system
Display-specification translation combines numbers, units, ratios, technical vocabulary and product identity. The broader framework is developed in Master Art of Translation | The Complete System for Moving Meaning Between Languages. Vocabulary depth connects to the Vocabulary Learning Hub, while comparison, ratio language and technical noun phrases connect to How English Works. The role of this article is narrower: it protects the exact display specification so a translated product remains the same screen.
FAQ
Is resolution the same as aspect ratio?
No. Resolution is a pixel matrix; aspect ratio is the proportional relationship between width and height.
Is 120 Hz the same as 120 fps?
No. Hz describes display refresh frequency; fps describes rendered or encoded frames per second.
Can 4K be translated as UHD?
Only when the source product uses the terms that way. Keep the exact pixel dimensions to prevent ambiguity.
Should ppi be changed to dpi?
Not automatically. Preserve the source technical unit and the object it measures.
Can I reverse 1080×1920 to 1920×1080?
Not if the source intentionally describes portrait orientation. Width-height order is part of the specification.
What is native resolution?
The physical pixel grid of the panel, distinct from other input modes the device can accept.
Should display size be converted from inches to centimetres?
Only when the target brief requires it. Keep the fact that the measurement is diagonal.
Can refresh rate depend on resolution?
Yes. Preserve mode-specific pairings when the source lists them.
Can AI translate display specifications safely?
It can assist with terminology, but exact values, units, orientation and compatibility claims should be independently verified.
What is the simplest rule?
Identify what every number measures, preserve the exact value and unit, and verify the target specification against the actual display.
Final checklist
- Is width-height order unchanged unless an explicit conversion was required?
- Are resolution and aspect ratio kept separate?
- Are refresh rate and frame rate kept separate?
- Are ppi and dpi used according to the source context?
- Is diagonal size still identified as diagonal?
- Are native and supported resolutions distinguished?
- Are mode-specific resolution/Hz pairings preserved?
- Are HDR, colour-depth and response-time qualifiers intact?
- Have marketing names been kept subordinate to exact specifications?
- Does the translated text describe the same physical display and supported modes?
Display-specification translation succeeds when the target reader sees the same screen: the same pixel matrix, the same proportions, the same refresh behavior, the same density and the same operating modes. Protect each technical property, translate the explanatory layer, and verify every specification against authoritative manufacturer data before release.