Workflow · 3 min read
How to Build Reusable Tag Collections
Turning one-off tag lists into a small library you actually reuse.
Name collections after content, not platforms
A collection called 'Instagram' becomes a dumping ground within a month. A collection called 'Studio process posts' stays meaningful, because its name tells you exactly what belongs in it and what does not.
Where platform differences matter, handle them at export time by formatting the same collection differently rather than by duplicating it.
Keep them small
Fifteen to twenty-five tags per collection is enough for almost any post. Larger collections stop being reusable because you have to edit them every time, which defeats the point.
Where collections live in TagGen
TagGen stores collections in your browser's local storage. They stay on the device you created them on, they are never uploaded, and clearing your browser data removes them. Export any collection you would not want to rebuild.