Convert ZPL from 203 to 300 DPI
Upgrade ZPL written for a 203 DPI printer to 300 DPI: coordinates, fonts and barcode module widths are rescaled ×1.5 so the label keeps its physical size. Embedded ^GF/~DG image data is not rescaled — the tool says so instead of hiding it.
Paste your code
Settings
Paste code or load the sample — the result appears below, with the line and severity of each finding.
Result
Converted ZPL
Warnings
How to convert 203 DPI ZPL to 300 DPI
- Paste the ZPL that was authored for a 203 DPI (8 dots/mm) printer — typically a supplier template or an integration that assumed a GK420 / ZD420-class device.
- The source is preselected as 203 and the target as 300; press Convert. Every coordinate (^FO/^FT), label size (^PW/^LL), font height and barcode module width (^BY) is multiplied by 1.5.
- Copy the output to your 300 DPI printer. Because 300 DPI packs 12 dots into each millimetre instead of 8, the extra dots reproduce the same physical layout instead of shrinking it.
- Read the warnings: ^GF/~DG bitmap data is passed through unscaled, so regenerate embedded logos from a higher-resolution source rather than trusting a stretched image.
When you need this exact direction
The classic symptom is a 4×6 shipping label that suddenly prints about two-thirds size with a large white margin after a printer swap: the ZPL still says ^PW812, but on a 300 DPI head 812 dots is only 2.7 inches. That happens when a warehouse upgrades from a 203 DPI workhorse to a 300 DPI model, or when a carrier template written for 203 DPI meets a high-resolution printer pool. Converting the file once — instead of reauthoring the template — keeps the supplier's layout intact.
Frequently asked questions
- Why does my label print small on the new 300 DPI printer? — ZPL measures in dots, not millimetres. 812 dots is 4 inches at 203 DPI but only 2.7 inches at 300 DPI — the printer renders exactly the dots it was told, so the layout shrinks. Rescaling the dot values restores the physical size.
- Will barcodes still scan after the ×1.5 conversion? — Bar and module widths (^BY, ^B3, ^BC parameters) are scaled together with coordinates, so the printed bars keep their physical width and ratio. As with any label change, verify a sample with your scanner before a production run.
- Why are embedded images not converted? — ^GF/~DG carry a fixed bitmap; multiplying its dimensions would require inventing pixels and produce a blurry, possibly unscannable graphic. The tool keeps the data untouched and warns you, so you can re-export the logo at 300 DPI from the original artwork.
Save your labels to your account and print them with DirectPrint — free account. Create free account
Same engine, same result: REST API, command line, or an AI assistant over MCP. Anonymous calls work; an API key raises the quota.
curl -X POST "https://api.labelixa.com/v1/dpi/convert?source=203&target=300" --data-binary @label.zplclaude mcp add --transport http labelixa https://api.labelixa.com/mcp # convert_zpl_dpi