Naming Your Sourdough Starter โ€” Practical Tips for Beginners

How to pick a memorable, useful name for your sourdough starter and simple conventions that help track its history and behavior.

What to Expect

A clear, consistent name for your starter makes maintenance, troubleshooting, and sharing much easier. This guide gives simple conventions and practical examples so you can pick a name that helps, not just entertains.

What you'll learn:

  • โœ“ Practical naming conventions that aid tracking and troubleshooting
  • โœ“ How to include key starter data in a name
  • โœ“ Ways to document changes so a name becomes a useful label

๐Ÿ’ญ A good name won't make your starter better โ€” but it will make you faster at identifying which jar is which and at communicating with other bakers [1].

What You Need

Must have:

Active sourdough starter

Shows rise and fall after feedings in a clear starter jar

โš ๏ธ Create a starter first โ†’ more

Kitchen scale

Used to measure feeds consistently

โš ๏ธ Get one โ€” consistent feeding is easier with a scale

Nice to have:

Why naming matters:

Clarity when you have multiple starters

If you experiment (whole grain vs. white, different hydrations), a clear name prevents feeding mistakes and confusion [1].

Useful shorthand for starter history

Embedding a date or flour type in the name records when the starter was created or last revived [2].

Easier troubleshooting and sharing

When you report issues or ask for help, a concise name that includes key metadata speeds communication [1].

Ingredients

For: Naming a starter (not edible)

Base name 1 A short, memorable word (e.g., 'Maya' or 'Field')
Flour code 1 Short tag for main flour (e.g., 'W' for white, 'R' for rye)
Hydration or type optional Add '65H' for 65% hydration or 'Levain' for build starters
Date or version optional YYMM or v1 to track lineage (e.g., '2401' or 'v2')

Step by Step

Pick a base name โ†’ add concise metadata โ†’ label jar and log in a notebook or app

1

Choose a short base name

5 min

Pick one memorable word that you like. Keep it 6 characters or fewer for readability.

โœ“ You can say it aloud easily and it's distinct from other kitchen labels
๐Ÿ’ก Avoid common food names that might clash with other labels in your kitchen.
2

Add flour and hydration tags

Append a short flour code and hydration or type. Example: 'Maya-R-100' = Maya, rye, 100% hydration.

โœ“ Someone else could tell basic starter properties from the label alone
๐Ÿ’ก Use capital letters for flour (W, R, A for all-purpose) and numbers for hydration
3

Add date or version

If you revived an old jar or created a new strain, add YYMM or vX. Example: 'Maya-R-100-2401' or 'Maya-W-65-v2'.

โœ“ Name includes a timeline cue to know which jar is newest
๐Ÿ’ก Keep the date near the end so the base name stays visible
4

Label the jar and log details

Write the name on the side of the starter jar with a waterproof marker and record feed ratios, temperature, and behavior in a notebook or phone note.

โœ“ Jar label matches your log and includes at least one feed record
๐Ÿ’ก A short QR code or note linking to a shared doc works well for collaborative kitchens [2]
5

Use the name when communicating

When asking for advice online or sharing with friends, include the name and the key tags (flour, hydration, age).

โœ“ People can immediately understand which starter you mean
๐Ÿ’ก Paste a short template: 'Name - Flour - Hydration - Age' for quick sharing
6

When to rename

Rename only when the starter's character changes significantly (new dominant flour, major lab feeding change, long dormancy). Update the log when you rename.

โœ“ Renaming is deliberate and accompanied by a note explaining why

What If It Doesn't Work?

Naming won't fix a sick starter, but good labels make problems easier to diagnose:

Confusing names

Likely: Lots of whimsical names without metadata

Fix: Adopt the base+flour+date convention and add a short log entry

Multiple jars, same name

Likely: Copying a starter into new jars and neglecting to rename

Fix: Add version numbers or dates to each jar's label

Name is too long to read on jar

Likely: Including too many details in the visible label

Fix: Keep jar label short (base+flour) and put extended notes in your log

Can't remember what tags mean

Likely: No reference system

Fix: Keep a single reference cheat-sheet in your starter notebook or phone

๐Ÿ’ช Simple, consistent naming makes maintenance faster and reduces feed errors โ€” small habits that improve baking outcomes over time [1][2].

What now?

Sources

  1. [1]
    The Perfect Loaf โ€“ The Perfect Loaf โ€“ Link
  2. [2]
    Plรถtzblog โ€“ Plรถtzblog โ€“ Link