How to Choose Fabric in Dressmaker

Quick answer

Choose a material by the request, not by the material. Read what the request names, read what the material shows on your own screen, write both down, and compare the two sets before you spend anything.

No cost or attribute value is published on this page, because none has been traced to a dated source. Dressmaker is a single-player sewing and fashion-design simulation released on Steam on 2026-09-21, developed by Cozy Lives and Free Lives, and the Steam store page describes the design, commission and sewing loop rather than a material table. Where a value is missing, the instruction is to leave it unknown rather than fill it with an estimate.

What a material record will hold, and why the table is empty today

A fabric row is deliberately narrow. It will carry three things: the material name, the cost the source states, and the attribute effects recorded for that material. Nothing else is stored, because every extra field would need its own evidence before the row could be published.

The fabric reference shows that table in its empty state and explains the same rule from the database side. At the September 28, 2026 check, the sources in scope did not list a material name together with both a cost and an attribute value. Steam announcements describe features rather than material tables, and the community guides that were read discuss money and achievements without publishing a list that could be transcribed row by row.

An empty table is the honest result of that check. A row built from a guessed price would look more useful than it is, and it would be quoted elsewhere long before anyone corrected it. The value of the empty state is that nothing on the page is wrong.

Comparing a material with a request without a published table

The comparison does not need a table. It needs two written lists that can be put side by side. Work through these steps in order.

1. Read the request. Write down every attribute the request states, including whether each is a floor, a ceiling or simply named. A limit you did not see is unknown, never zero.
2. Write the material name. Record it exactly as your screen spells it, so a later note can be matched to the same material without ambiguity.
3. Record the cost as displayed. Copy the figure you can see, with the unit it is quoted per. Do not convert it to a per-garment figure; that needs a quantity you do not have yet.
4. Record each attribute the material shows. One line per attribute, written as the interface states it rather than translated into a scoring system this site cannot verify.
5. Compare and mark the gaps. Put the two lists next to each other and mark every row where one side is missing. Those gaps are the real output of the exercise.

Enter the values you trust into the commission checker so the arithmetic is repeatable and the inputs stay auditable. The checker does not search for a material or promise a delivery; it tests one candidate against the request you typed, which is exactly the decision this guide is about.

How to handle an unknown value

An unknown value is not zero and it is not a guess. Treating it as zero makes a comparison look decisive when nothing was measured, and a guess is worse because it travels: a fabricated figure is copied into other people's notes within days and is nearly impossible to trace back to its source. The honest entry is blank, with a note that the interface did not show it.

Unknowns are also actionable. If a material's cost is unread but its attributes are clear, the material can still be compared on attributes alone, and the cost gap can be closed later by reading it again. Naming the gap is what makes the next session faster; hiding it with a plausible number makes the note useless the moment it is tested.

Apply the same rule to the request side. A request that seems to omit a limit has an unknown limit, not an unlimited one, and a garment cannot be declared safe against a limit nobody has read.

What transfers from real sewing: weight, drape and stretch

As in real garment sewing, three properties usually decide how a cloth behaves on the bench. Weight is how heavy the cloth feels, and heavier cloth tends to hang with more structure while lighter cloth tends to follow the body. Drape is how readily the cloth folds and curves rather than standing away from the form. Stretch or give is how much the cloth moves along one direction when it is pulled.

These are general sewing behaviours, and this page does not claim the game models any of them. What it does say is that they are useful hypotheses. If two materials differ in one of these properties and everything else in the build is held constant, the difference between the two finished garments is evidence about the direction of an effect even when the size of that effect stays unknown. The quality guide covers how to run that kind of one-change test and what to write down.

Community claims to treat with care

Community material is useful because it shows a method being performed, and it is dangerous when a number inside it is repeated without its label. The write-up 'Thing's I've Learned' by Seerolz covers measuring, fabric choice, pattern cutting, sewing, accessories and quality (Steam Community guide) — community-reported, checked 2026-09-28. A second write-up, 'How to make money in DressMaker', discusses off-the-rack dresses and gives a sell-price figure that it labels as an estimate (Steam Community guide) — community-reported, checked 2026-09-28.

Both are recorded here as attributed, dated, community-reported material. Neither is official, and this page repeats no figure from either. If a claim from them matters to a build, test it with one change at a time and compare the result against the method rather than against the number. The source register records what has been read and when.

What stays unknown

This page publishes no costs, no attribute values and no quality formula, and the list below is the reason. None of the following has been traced to a dated source that this site has read:

• The cost of any material, in any unit.
• The attribute values any material carries, and how the interface names them.
• How material attributes combine into a finished quality score, or whether they do.
• How much of a material a given pattern consumes.
• Whether weight, drape and stretch are simulated at all.
• Whether the material list changes between patches, and how it is restocked.

These stay unpublished rather than estimated. When a source states one of them, the row is added with the date it was read. Until then the instruction is to read the value from your own screen and write it down, then compare it against the request you are answering. The commission method shows where that comparison sits in the loop, the pattern cutting guide covers what happens to the cloth next, and the checker holds the arithmetic while the reference is empty.