I am currently utilizing Additional Categories for K2 and was wondering with the new feature in K2 v3 that offers the use of extra fields for tags, I was wondering what limitations would I potentially experience with using K2 Tags instead of Additional Categories?

Note: I use extra fields for virtually everything (item & list images, metadata, social tags, etc.)

I plan on using two K2 tags two ways:

1) Explicit tags to be used as "sub-categories" by way of menu links (/blog/phones)
2) General tags for in-content links to topics, brands, etc. (/tags/iphone)

The only limitation I can see in your scenario is related to the K2 Content Module which does not support fetching K2 Items by tag (yet).

Just to make things more clear. K2 2.7.0 will include a tag filter in the K2 content module. The same filter will be included in K2 v3 also.

Thanks guys - hey @Lefteris, so with that addition coming, are there any other limitations of using tags vs additional categories in K2 v3?

There are differences between tags and categories:

1. Categories can be nested, tags not.
2. Categories can have images and content.
3. Each category can have it's own settings for displaying content. Tags have global options for that.