Why Flexo Press Speed Drops as Colour Count Rises

The Reprint Job That Should Have Run Twice as Fast

A shop we talked to had quoted a straightforward reprint: same label, same substrate, same die — but the brand had gone from a 4-colour mark to a 7-colour rebrand with a metallic accent. The estimator pulled up last year's job ticket, saw the press ran at a certain line speed on the original 4-colour version, and used that same speed to figure run time on the new 7-colour job. Same press, same operator, same die — why would it run any differently?

It ran nowhere close. The extra three stations meant more interstation drying, tighter register tolerance on the fine copy, and a metallic ink that needed longer dwell time before the next station could safely lay ink on top of it. The job that was scheduled for a single shift bled into a second. The labour and press-time numbers on the invoice didn't match the numbers on the quote, and nobody could point to exactly why — because the estimate had never treated speed as something that changes with colour count in the first place.

By the end of this piece, you'll be able to build your own press-speed curve by colour count and use it instead of a single flat number on every job.

Why Flexo Press Speed Drops as Colour Count Rises

Every CI flexo press has a mechanical top speed printed somewhere in its spec sheet — a number that gets quoted in sales conversations and sometimes gets carried straight into an estimate. But that top speed almost never survives contact with a real multi-colour job. The number on the spec sheet describes what the drive train can physically do; it says nothing about what the ink, the substrate, and the register tolerance on that specific job will allow.

That's the core idea behind flexo press speed by color count: speed isn't a fixed property of a machine, it's a curve, and the curve bends downward as you add stations. A 2-colour job on coated stock might run near the press's practical ceiling. A 7-colour job with a metallic and fine reversed text on the same press, same substrate, might top out at a third of that speed — not because the press got slower, but because the job now has more places where something can go wrong at high speed.

Treating press speed as one number for the whole shop is the single most common way an estimate quietly diverges from the invoice.

What Actually Slows the Press: Drying, Registration, and Web Tension

Three mechanisms do most of the work of bending the curve down as colour count rises.

Interstation drying. Whether a press uses UV curing lamps or hot-air drying between stations, each station needs enough time — enough web travel at a given speed — for the ink just laid down to set before the next station prints on top of it. Add a station, and you've added one more place in the web path where ink has to be dry enough to accept the next colour without smearing or trapping incorrectly. Push the speed up without giving the ink enough dwell time, and you get smearing, poor trapping, or dot gain that ruins colour match. Metallics and heavy opaque whites are usually the worst offenders here, because they carry more film weight and take longer to set.

Register tolerance. More colours means more chances for misregistration, and label graphics with fine text, thin rules, or barcodes leave very little room for drift between stations. An operator watching register creep on a 7-colour job will back the speed down long before they'd need to on a 2-colour job, simply because there are more places for the stack-up of small errors to become visible.

Web tension and tracking. Every additional print station is another nip point the web has to travel through cleanly. On thin or unsupported substrates — think thin films or unsupported foils — more nip points mean more opportunity for flutter, tracking drift, or tension-related streaking at speed. The press doesn't need to be told to slow down for this; it gets slowed down by the operator watching it happen.

None of these three mechanisms are unique to any one press brand or shop. They're why the press-speed curve exists at all, and why it bends the way it does — steeper drops as you add stations, and a sharper drop again once you add a metallic, heavy white, or particularly delicate substrate into the mix.

Building a Press-Speed Curve You Can Actually Use

The fix isn't a more precise single number — it's replacing the single number with a curve: practical run speed, mapped against colour count, built from what your press actually does on your substrates, not what the spec sheet claims it can do.

In practice that means logging actual run speeds by job, tagging them by colour count and substrate class, and building a simple table: 1–2 colours run around one speed, 3–4 colours run slower, 5–6 slower still, and 7+ — especially with a metallic or heavy white in the mix — slower again. It doesn't need to be a scientific curve fit. Even a rough table beats a single flat number, because it captures the direction and the rough magnitude of the drop.

This is exactly the calculation FlexoCommand's flexo quoting engine is built around: press configuration includes a speed curve by colour count, so a quote for a 7-colour job automatically pulls a different run speed than a quote for the same press on a 3-colour job — instead of relying on whichever number happened to be in someone's head that day. It's one input among several in a full estimate; run speed alone doesn't tell you the makeready waste a job will burn getting to colour, which is its own piece of the estimate worth understanding on its own.

A Worked Example: Estimating Run Time from a Speed Curve

Here's a simplified, round-number version of the arithmetic — a worked example, not a claim about any specific press.

Say a shop's logged history produces a rough curve like this: 2-colour jobs run near 700 feet per minute on their main CI press; 4-colour jobs settle around 500 fpm; 6-colour jobs around 350 fpm; and a 7-colour job with a metallic drops to roughly 250 fpm once the extra drying dwell is accounted for.

Now take an order for 50,000 labels, with a 5-inch repeat — meaning roughly 12 labels per linear foot of web, or about 4,167 linear feet of web needed to produce the run.

• At the 4-colour speed (500 fpm): 4,167 feet ÷ 500 fpm ≈ 8.3 minutes of pure run time.
• At the 7-colour speed (250 fpm): 4,167 feet ÷ 250 fpm ≈ 16.7 minutes of pure run time.

Doubling the colour count roughly doubled the run time in this example — before makeready, before drying issues that force a mid-run slowdown, before anything else. An estimate built on the 4-colour speed for a 7-colour job understates run time by half in this illustration. Multiply that gap across press-hour rate and labour, and it's easy to see how a reprint quote comes in profitable on paper and loses money on the floor.

Where the Speed Curve Fits Into the Rest of the Estimate

Press speed by colour count is one input, not the whole estimate. A complete flexo quote still needs makeready waste, per-colour plate cost, die amortisation, and MSI-based substrate pricing layered on top of run time before you get to a defensible per-label cost — the full mechanics are laid out in how to estimate a flexo label job from scratch and, at a higher level, in the complete guide to label estimating.

In eight years building production label-quoting software, the single most common gap between a quote and the eventual invoice traces back to exactly this: one flat press-speed number applied to every job regardless of colour count. The first quoting engine I built, LabelDockets, ran live at a multi-press narrow-web converter, and a colour-count-aware speed table was one of the first things we added to it, because it's where a surprising share of estimate error actually lives.

If you want the underlying formulas — speed curves, makeready allowances, plate cost, MSI pricing — laid out in one reference you can keep at your desk, the Estimating Reference & Formula Guide walks through each of them with worked examples. And if you'd rather see how a press-speed curve behaves inside a live quote instead of a spreadsheet, FlexoCommand's pricing page outlines how the flexo engine handles it press by press.

If this kind of estimating-math breakdown is useful, it's worth getting the next one directly — subscribe to get future pieces on flexo cost mechanics as they're published, rather than checking back for them.