- Kohya
- Trigger words
- Dataset packaging
- ohwx
What Does ohwx Mean? Kohya Folder Naming Explained
ohwx is a rare LoRA trigger token, not a Kohya keyword. How 10_ohwx woman splits into repeats and class tokens, plus the parent train_data_dir rule.
If you have seen a Kohya folder named 10_ohwx woman and wondered what ohwx means, the short answer is: it is not a special Kohya keyword. It is a rare trigger token that the community popularized for character LoRAs. The number before the underscore is the repeat count; everything after is class tokens (trigger + class noun). This article separates those pieces so you can name folders and write captions without cargo-culting a meme string.
What does ohwx mean?
ohwx is an invented, low-frequency token. Trainers use it because Stable Diffusion-family models have almost no prior meaning for it, so it is easy to bind to your subject. Popular alternatives include sks and zwx, or an invented proper name that is not a celebrity. Nothing in Kohya or sd-scripts requires the letters o-h-w-x specifically.
Caption vs folder
Anatomy of 10_ohwx woman
In classic DreamBooth-style subdirectory loading, Kohya splits the child folder name on the first underscore:
| Part | Example | Meaning |
|---|---|---|
| Repeats (N) | 10 | num_repeats: how many times each image in this folder is seen per epoch |
| Class tokens | ohwx woman | Fallback caption / class: rare trigger + broad class noun |
10_ohwx woman→ 10 repeats, tokensohwx woman30_cat→ 30 repeats, tokencat(object-style class, no rare trigger)
Folders that do not start with an integer are ignored in this mode. Choose N from the steps math on how many images a LoRA needs, not from copying someone else’s folder name.
Where train_data_dir must point
Point train_data_dir at the parent of the N_… folders, not at the folder that contains the PNGs. Kohya looks for named children under that path. Aiming one level too deep is the usual cause of “No data found.” Full packaging steps live in Kohya folder names and Civitai zip layout.
train_data/ ← train_data_dir
└── 10_ohwx woman/
├── 001.png
└── 001.txtWhen folder names do not matter
If you train with a Kohya dataset TOML, num_repeats and class_tokens are set in the config and the N_name convention is ignored. Point image_dir at the directory that directly contains images, and keep sidecar captions. Civitai’s on-site trainer also ignores Kohya folder names: it wants a flat zip of image + .txt pairs.
Should you keep ohwx or invent your own?
Keeping ohwx is fine if you like community examples. Inventing your own rare token is also fine and can reduce collision if you publish many LoRAs. Either way: same spelling in every caption, pair with a class noun (woman, man, person), and do not use a real name that already means something to the base model.
Frequently asked questions
Is ohwx required by Kohya?
No. Kohya only requires that DreamBooth-style child folders start with an integer repeats count. The text after the underscore is whatever class tokens you choose.
Should ohwx appear in every caption?
Yes if that is your trigger. Put the same rare token first in every caption so the LoRA binds identity to it. Folder class tokens are only a fallback when a sidecar is missing.
What does the 10 in 10_ohwx woman mean?
It is num_repeats: each image in that folder is shown 10 times per epoch in classic subdirectory loading. Pick N from your target step count, not from tradition.
Do Civitai zips need an ohwx folder?
No. Civitai wants flat image and .txt pairs at the zip root. Repeats and class settings are chosen in the web UI, not in folder names.