Skip to content
CiderHQ
Search

Fault

Ropiness

Cider that pours thick and pulls into an oily thread, caused by lactic acid bacteria secreting long-chain glucan polymers into the drink.

Also called oiliness, graisse, sickness.

Severity
Quality — the drink is worse for it
Where it starts
Maturation, Blending, Storage
Can it be fixed?
Partly — it can be reduced, not removed
When you notice it
Maturation, Storage
Signs
5 recorded

What it is

Ropiness is a texture fault: the cider becomes viscous and, when poured, forms a continuous oily rope or thread rather than breaking into droplets. It is caused by lactic acid bacteria producing extracellular polysaccharide — chiefly beta-glucan — which builds a polymer network in the liquid. The flavour is often barely affected, which is what makes it so disconcerting. Historically known in French cider as graisse and in English farmhouse usage as the cider being sick.

What you notice

Grouped by sense, because that is how the fault presents itself rather than how it works.

In the mouth

  • Cider that pours as a thread or rope instead of breaking upThe classic demonstration: tip the vessel slightly and watch the last of the stream.
  • A slippery, oily, almost egg-white mouthfeel

To look at

  • Liquid that looks slightly viscous when swirled, clinging to the glass

On the palate

  • Flavour that is largely unchanged, or only slightly dullerA fault you can see and feel but often cannot taste.

How the batch behaves

  • Cider that has been sitting undisturbed in a warm cellar for months

The words for it: Ropy. Each links to what produces it.

When it appears. In a finished, low-acid, low-alcohol cider or perry that has been standing. It develops over weeks and is often first noticed when the liquid is poured.

What is known about detecting it

It is one of the few faults on this list that is diagnosed by pouring rather than by smelling or tasting, and it is more common in perry than in cider because the conditions that favour it — low acid, low alcohol, residual sugar — are perry’s ordinary finishing state.

Various journals, Cider and Perry Academy (Peter Mitchell)

What it is mistaken for, and how to tell

One observation per rival, chosen because it separates them rather than because it describes either. Several of these are not faults at all — a style feature, a normal outcome, or the fruit behaving as it does.

What is actually happening

The chemistry or microbiology behind it. Understanding the mechanism is what makes the prevention make sense rather than being a list of rules.

Certain strains of lactic acid bacteria synthesise exopolysaccharides and secrete them into the surrounding liquid. In cider the important polymer is a beta-1,3-glucan with beta-1,2-glucosyl side chains, produced by a small number of strains carrying the relevant glycosyltransferase gene. The polymer is long, highly hydrated and forms a network that raises the viscosity of the whole liquid at very low concentration.

The organisms involved are Pediococcus species, Lactobacillus collinoides, Oenococcus oeni and Leuconostoc mesenteroides, though only particular strains within these species have the capability. This is why an entirely normal malolactic fermentation in one cellar is harmless and in another produces ropiness: the species is not the determinant, the strain is.

Conditions favouring it are those favouring lactic acid bacteria generally — high pH, low or absent free sulphur dioxide, residual sugar, warmth and stillness — with the addition that the polymer accumulates over months rather than appearing suddenly. Low-acid ciders from bittersweet fruit are the classic victims.

The polymer is a physical structure rather than a chemical modification of the cider, which is the reason for the fault’s one redeeming feature: the network can be broken. Vigorous agitation shears the chains, and the viscosity drops immediately. The polymer is still present, and the bacteria are still there to make more.

How it happens

Causes, with the stage each originates at and how often it is the explanation.
CauseStageHow often
Lactic acid bacteria active in a high-pH, low-acid ciderMaturationcommon
Residual sugar available to spoilage lactic bacteriaMaturationcommon
No free sulphur dioxide during a long, still maturationMaturationcommon
A blend made entirely from low-acid fruitBlendingoccasional
Warm storage in an undisturbed vessel over many monthsStorageoccasional
Equipment carrying a resident population between batchesMaturationoccasional

Can it be put right?

Most cider faults cannot be reversed. Where that is the answer it is given plainly — an honest 'this batch is what it is' is more useful than a procedure that will not work.

Corrective options and how well each actually works.
OptionEffectivenessWhat it involves
Break the polymer by vigorous stirring or beatingPartialThe traditional response and it genuinely works on the texture, immediately. It does not kill the bacteria and does not stop the polymer being made again, so it must be combined with stabilisation to be worth anything.
Stabilise after breaking the ropePartialFiltration, pasteurisation or an appropriate sulphite addition after agitation prevents recurrence. This combination is the only route that actually resolves the fault, and it is more work than most home producers expect.
Fine or filter the polymer out without agitationUnlikely to workA viscous cider blinds filter media almost immediately. Breaking the network first is a prerequisite rather than an option.
Wait for it to clear on its ownUnlikely to workIt does sometimes resolve as the bacteria die back and the polymer settles, over a long period, but a cider left to it is a cider left exposed to everything else the same organisms do.
On dosages

CiderHQ gives no additive dosage figures. An addition is a food-safety decision that depends on legal limits, on the juice in front of you and on what you are protecting against, and the right figure comes from your supplier’s or regulator’s own guidance rather than from a general reference.

Preventing it

More on this

Ropiness is the most physically startling of cider faults and one of the least damaging to flavour, a combination that makes it memorable. A cider that pours like thin oil and forms a thread from the tap looks ruined and often tastes almost normal, and the traditional English name for the condition — the cider being sick — captures the impression rather well.

Its association with low-acid West Country cider is not accidental. Everything that makes a bittersweet blend what it is also makes it hospitable to lactic acid bacteria: high pH, low malic acid, long slow maturation in wood at cellar temperature. The sharp fruit in a traditional blend is not there only for the palate.

The traditional remedy of beating the cider with a stick or a whisk is real and it works, because the fault is a physical network rather than a chemical change. What the tradition did not have was any way of stopping the bacteria afterwards, which is why the sickness so often came back. A modern maker who breaks the rope and then does nothing else has reproduced exactly the historical outcome.

The most useful takeaway is diagnostic. A cider going ropey is direct evidence of an unrestrained lactic population, and the same population produces faults that are far harder to live with, mousiness among them. Ropiness is worth treating as a warning about the cellar rather than as an isolated curiosity.

The compounds involved

The organisms involved

Where in the process it arises

Faults it is confused with

These present similarly. What separates them is set out on each page.

Where this comes up in a guide

The link lands on the step where the fault arises rather than at the top of the pathway, because that is where the decision that causes it is taken.

What people ask next

Questions readers ask about the things this page mentions. Each one goes to the section that answers it rather than to a page written to receive the question.

Where to go next

Sources

What this page rests on. Where a source is marked as registered rather than read, CiderHQ is recording that the body is authoritative on the subject without claiming to have worked through the document itself. See our evidence policy for what each state means.