Home›Test pages›Printer reference›Test patterns
Printer Test Patterns Explained
Every mark on a printer test sheet exists to answer one specific question. Read the sheet in the wrong order and you will diagnose the wrong fault with complete confidence.
Set scaling to 100%. Choose Actual Size in the print dialog, never Fit to page — scaling distorts every measurement on this sheet. The Download PDF button hands you that same sheet as a ready-made file, so there is no scaling decision to get wrong.
How to print the Printer Test Patterns Explained
- Read the whole sheet before forming any opinion.
- Identify the nozzle rows: they test ink delivery and nothing else.
- Move to the colour bars and grey ramp for lay-down and tone.
- Check converging lines for effective resolution.
- Finish with alignment marks for skew and registration.
- Only then decide whether the printer, the paper or the driver is at fault.
Reading the result
| You can name what each section measures | The sheet becomes an instrument rather than a pattern of ink. Each mark now rules a fault in or out. |
| One section looks wrong but you cannot say which fault | You are reading the sheet as a whole. Isolate the section first, then ask what that section is for. |
| Several sections are wrong at once | A shared cause. Nozzles, paper feed and driver scaling each affect multiple regions, so count the regions before blaming a single part. |
| Everything is correct on the test sheet but output is bad | The fault sits outside the print path: application colour management, a corrupt profile, or the source file itself. |
| A fault appears only on one paper type | Media selection rather than the printer. Check the driver is told which stock is loaded. |
Also check
- Nozzle check — The first pattern you should learn to read: it measures ink delivery alone, which is why it comes before every other interpretation.
- Gradient page — The clearest example of a mark whose meaning changes with viewing distance — exactly the kind of judgement this guide is about.
- Alignment page — Registration is the final section of any test sheet, and the only one that needs a cross-hair rather than a tone ramp.
Related test pages
- DPI Chart printer test page — Printers advertise one resolution and deliver another. This chart measures what you actually get.
- Alignment printer test page — If lines that should be straight come out crooked, or text looks doubled, the printhead is out of alignment. This sheet measures it.
Frequently asked questions
Which part of the test sheet should I check first?
The nozzle rows, because they are the most common fault and the cheapest to fix. A clog shows up as a missing stripe in the rows and is usually cleared by a cleaning cycle. Checking ink delivery first means you never waste time interpreting a gradient that was drawn by half the nozzles.
What is the difference between a test pattern and a test page?
A pattern is a specific arrangement of marks designed to measure one thing. A test page is a sheet carrying several patterns together so you can assess a printer in a single pass. The charts on this site are test pages made of patterns, which is why reading them in order matters.
Do laser printers need the same test patterns?
Mostly, but not identically. Nozzle rows are meaningless on a laser — there are no nozzles — while gradient, banding and registration marks are just as useful. Fuser problems show up as repeating bands and drum faults as vertical streaks, both of which the gradient page exposes clearly.
Why does the pattern change with paper size?
Because it is generated to the dimensions you choose rather than being a fixed picture. Scaling a drawing up or down would change line spacing and dot pitch, and those are exactly the measurements the sheet is supposed to provide. Pick the size of the paper loaded and the geometry stays true.
How often should I print a test page?
Weekly for a printer in daily use, monthly for one used occasionally, and always after a cartridge change, a paper jam or any print that looks wrong. Patterns are cheap; a misdiagnosed fault is not.