Per‑asset versioning inside multi‑asset projects

Hi BugSmash team,

first of all, I really like your tool and the way projects and versions work for single assets (one website, one PDF, one image, etc.).

However, in real client work there is one major limitation for me: handling multiple variants inside one project.

Typical use case 1 – Logos
When I design a logo, I often present several logo concepts in parallel, for example 5 logo options in one round for the client. I upload all 5 logos so the client can comment directly on them. The client might only request changes on 2 of those 5 logos.
If I now upload a “new version” of the project, the entire project gets a new global version number, even though only 2 logos have actually changed. This makes it hard to compare “Logo 2 – old vs. Logo 2 – new” directly on a per‑logo basis, because the versioning is tied to the whole project, not to each individual asset.

Typical use case 2 – multiple layout proposals
The same happens with website layouts:
I might present 3 layout proposals (A, B, C) in one project so the client can compare and comment on all of them. Later I only revise layout B and C, not A. Again, a single project version number for everything is not ideal, and it becomes confusing if we want to do precise before/after comparisons per layout.

What I would love to see
I would really appreciate a feature that allows per‑asset versioning inside a project when a project contains multiple images (or screens). In other words:

• A project can hold multiple assets (e.g. Logo 1, Logo 2, Logo 3, Logo 4, Logo 5).

• Each asset can have its own versions (Logo 2 – V1, V2, V3), with direct visual comparison between versions of that specific asset.

• The project itself is then more like a “container” for related assets, but the version logic works on the level of each asset, not only on the whole project.

From my perspective, this would avoid the need to create a separate project for every single logo or layout variation, which quickly becomes messy for clients. At the same time, it seems conceptually close to what you already do for single‑asset projects with version comparison, just applied per asset instead of globally.

Is this something you could consider adding to your roadmap?
For agencies and designers who work with multiple concepts in parallel (logo sets, layout sets, visual explorations), this would make BugSmash much more practical.

Thank you very much for considering this and for your great support.

Best regards,