Enter a value in typographic points to calculate the corresponding amount in CSS pixels at 96 ppi. The result updates from the published unit relationship and includes a reverse check so a misplaced factor is easier to spot.
A reproducible example uses 12 pt. Applying the rule gives 16 px, or 12 × 1.333333333333 = 16.
The nearby values show how CSS pixels at 96 ppi changes proportionally with typographic points.
The move from typographic points to CSS pixels at 96 ppi is common in web typography, design handoffs, layout specifications, and interface mockups.
Both pt and px describe typography, so points to pixels changes the representation rather than the measured quantity.
Carry the unrounded CSS pixels at 96 ppi value through intermediate arithmetic. Round once when the points to pixels result is presented.
A coarse measurement in typographic points remains coarse after it is written in px, even though conversion creates a decimal.
Read every input marked pt as typographic points. Read the answer marked px as CSS pixels at 96 ppi. The numerical points to pixels relationship uses 1.333333333333.
Resolution units describe pixel density, while standalone pixel and point units describe lengths under a stated rendering convention. Check the complete unit name before applying this points to pixels relationship to an outside data source. That notation keeps a later reader from applying the points to pixels factor in the opposite direction.
For another destination unit after points to pixels, continue with the general typography converter. A connected conversion is pixels to points.
The practical question in web typography, design handoffs, layout specifications, and interface mockups is usually not the factor alone; it is whether the CSS pixels at 96 ppi result still represents the intended typographic points quantity.
Read the unit, magnitude, and precision together. Those three checks keep a valid points to pixels calculation from being attached to the wrong object or operating case.
Write the source value with pt before doing any arithmetic. For points to pixels, Multiply typographic points by 1.333333333333 to obtain CSS pixels at 96 ppi.
Keep the px label on the answer, then test it backward. Divide CSS pixels at 96 ppi by 1.333333333333 to return to typographic points.
The scale begins with one pt and ends at 1.333333333 px. Looking back from px, the reciprocal magnitude is 0.75 pt.
A paper calculation can cross out pt only when the conversion ratio puts that symbol in its denominator. This exposes a flipped factor.
Copy CSS pixels at 96 ppi with its px label into the next step. Keeping the corresponding typographic points value makes the points to pixels result traceable if a later total looks wrong.
Estimate CSS pixels at 96 ppi from the size of 1.333333333333 before reading the exact answer. A large disagreement suggests a transposed unit.
Next convert the px result back to pt; it should agree with 12.
Multiply typographic points by 1.333333333333 to obtain CSS pixels at 96 ppi. Divide CSS pixels at 96 ppi by 1.333333333333 to return to typographic points.
Use the inverse relationship on the calculated px value. If it does not return the entered pt amount, recheck the factor and unit order.
Yes. Zero pt maps to zero px because points to pixels has no zero-point offset.
A comparison may need fewer px decimals than a later formula. Choose the final rounding from the purpose and the quality of typographic points.
The formula can process a negative pt amount. Some real-world typography quantities, however, are constrained to nonnegative values.
Inspect the full typographic points definition, the CSS pixels at 96 ppi target, and the points to pixels factor. Small differences usually come from rounding; larger ones often indicate another standard.