Perhaps the better way to look at it is the reverse: what benefit do tags add to your organization such that adding another one is *not* worth it. In some ways, it's like the similar question, when tags aren't available, of what organizing info might go into the folder hierarchy vs. what might go into a file name itself. So if a tag is important for grouping multiple files based on some common attribute, I would argue that there is *no limit* to how many of them you should use. If, however, it's an attribute that is unique to a single file, then maybe it shouldn't be (or be thought of as) a tag at all. 89cf45e083f227cd96fafd923c9a41c9dc8e58ea14240386f3d2f000c6d93d63