These tag list(s) contain tags + their aliases (active & deleted + chars/artists/franchise tags) from Danbooru and/or e621 and are for use with sd-webui-tagcomplete extension and ComfyUI-Custom-Scripts autocomplete feature (or AutocompletePlus / comfy-ex-tagcomplete) as well as Krita AI Diffusion, Stability Matrix and SwarmUI (and lots more probably).
There are 3 main versions.
Danbooru - Danbooru tags only (best for Illustrious and NoobAI/Pony if not using e621 knowledge)
e621 - e621 tags only (best for e621 models/usage only; e.g: NoobAI)
danbooru_e621_merged - a merge of both Danbooru and e621 tags (best for NoobAI/Pony based models especially if you plan on using e621 stuff and your extension doesn't support loading multiple tag lists at once)
There's also 🖌️ Krita AI Diffusion compatible tag lists inside the corresponding folder.
There is a 🇨🇳 Chinese version made by @UrielGnoyzaki (comment).
The a1111-sd-webui-tagcomplete extension already comes with the 22.12.2024 tag lists so you don't need to download those from here.
22.12.2024 is the recommended version for overall use case if you don't want to switch a lot. "01.09.2025 ChenkinNoob 01" and similare are release made for the model of the same name, but not exclusive to, just use them for what you see fit. The ones that are have a more recent date are mostly there for future proofing and the older ones usually have worse filtering/merging but the site-indivdual tag lists should be ok to use.
You can find the full archive of all tag lists (including other misc stuff like some raw data) that have been made on the archive GitHub repository. (auto updates every months as GitHub actions artifacts, and uploads to repo every 3 months)
The script(s) with which I made these tag lists is open source on my GitHub.
Some info on the install process for some tools can be found on the main page of the repo (readme.md)
Some rather trivial info:
NoobAI 1.1/1.0 Eps/Vpred knowledge cutoff for danbooru is roughly before 23rd October 2024
NoobAI's e621 dataset is only up to date until early 2024 (Yi from Nine Sols will won't work for example) meaning older tag lists for e621 specifically might feel better to use
Illustrious v0.1/1.0-2.0 danbooru knowledge cutoff is roughly june 2024
RouWei has a slightly more up to date dataset (april 2025 for 0.8, dec 2024 for 0.7 or so) for those who use it and see this
Generally I don't think much has changed over the few months so the 22nd december 2024 will still be the recommended version.
The Danbooru tag scraping part was originally borrowed from BetaDoggo over here (many thanks)
Also a thank you to e621 for having every list easily accessible
also pandas dataframes are kinda cool.
Description
Not Recommended. Reason is in the 22.12.2024 Refined "About this version"
Krita AI Diffusion compatible tag lists included.
Minimum post count threshold is 25 AND 2 (there's 2 versions in the zip, you can choose which one you want)
Characters/Artist/franchise names + Active and deleted alias tags are included (pending alias tags from e621 are excluded)
All subsequent releases will include the Krita AI compatible version including their original versions in case you lose/overwrite them i forgot that part this time lol
FAQ
Comments (10)
The merge is great, but you didn't fix the different tag categories, since e621 and danbooru don't use the same categories. For example: category 5 on danbooru is quality tags while on e621 it's species tags.
I actually have different category index meanings commented in my code but I didn't pay much attention to it since I don't know how I would fix it.
I guess I could move species tags to third category/category 2 which seems to be nothing for danbooru for some reason but otherwise idk
I also don't think any program that is compatible with these lists actually has an issue with dbr and e6 using the same category index for different things, but if there is some type of incompatibility in a program please tell me
Best I can think of right now is merging category index 7 of e6 into DBR category index 5 since both are meta tags but not sure what to do about e6 species category
@DraconicDragon For A1111, forge, reforge tag autocomplete extension
You could just create a new one of these specificaly for the merge:
"danbooru": {
"-1": ["red", "maroon"],
"0": ["lightblue", "dodgerblue"],
"1": ["indianred", "firebrick"],
"3": ["violet", "darkorchid"],
"4": ["lightgreen", "darkgreen"],
"5": ["orange", "darkorange"]
},
"e621": {
"-1": ["red", "maroon"],
"0": ["lightblue", "dodgerblue"],
"1": ["gold", "goldenrod"],
"3": ["violet", "darkorchid"],
"4": ["lightgreen", "darkgreen"],
"5": ["tomato", "darksalmon"],
"6": ["red", "maroon"],
"7": ["whitesmoke", "black"],
"8": ["seagreen", "darkseagreen"]
},
@foxmlg I've replaced the most recent uploaded version with one that has an additional merged tag list added that should be compatible the way you were talking of
The JSON for the colors would be
"danbooru_e621": {
"-1": ["red", "maroon"],
"0": ["lightblue", "dodgerblue"],
"1": ["indianred", "firebrick"],
"3": ["violet", "darkorchid"],
"4": ["lightgreen", "darkgreen"],
"5": ["orange", "darkorange"],
"7": ["lightblue", "dodgerblue"],
"8": ["gold", "goldenrod"],
"10": ["violet", "darkorchid"],
"11": ["lightgreen", "darkgreen"],
"12": ["tomato", "darksalmon"],
"14": ["whitesmoke", "black"],
"15": ["seagreen", "darkseagreen"]
}
I'm gonna hide this comment since it's not relevant anymore for people finding it in the future. The danbooru e621 merged list now comes by default (22nd december version) with sd webui tagcomplete. The JSON for the colors, if missing, can be found here https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/releases/tag/3.2.0 (should be the same except the that it's named "danbooru_e621_merged" because thats the file's name and that number 6 for invalid color was added)
The a1111-sd-webui-tagcomplete extension now comes with the 22.12 version (it doesn't need the refined version) of the tag lists by default including the merged list. Wiki Links also work with it: danbooru tags will link to Danbooru and e621 tags will link to e621
really nice
Is there a way to give priority to danbooru tags in the merge?
For example if I put "knees_together_feet_apart" it gets redirected to knock-kneed.
But if I put "knees_touching" it get's redirected to "knees_together_feet_apart"
Illustrious models with noobai tags like ntrmix don't seems to understand knock-kneed, but knees_together_feet_apart is good.
Same with "1girl" that get redirected to "female" while it shouldn't
Hi, I just made a test version which you can find here https://github.com/DraconicDragon/dbr-e621-lists-archive/tree/main/tag-lists/danbooru_e621_merged
The CSV files with the "refined-aliases" suffix are the ones that should prevent this problem
The difference over the normal 2024-12-22 CSV files is that the refined-aliases ones have the/an alias tag removed if it is the same as an existing actual tag
(Direct link to load the version with post count threshold of 25: https://raw.githubusercontent.com/DraconicDragon/dbr-e621-lists-archive/refs/heads/main/tag-lists/danbooru_e621_merged/danbooru_e621_merged_2024-12-22_pt25-ia-dd-ed.csv)
@DraconicDragon Thanks, perfect!