An approval should belong to one version, not every version that comes after it.

That idea shaped FrameProof, a visual review workspace I built with Bolt.new for designers and small creative teams.

Instead of separating the artwork from the conversation, FrameProof brings them together:

Pin feedback to the exact part of an image.

Keep comments and replies connected to each revision.

Compare versions side by side or with a slider.

Record an approval or request changes on the version being reviewed.

The detail I cared most about: uploading a new revision does not carry forward an earlier approval. The decision stays attached to the work that earned it.

I also built expiring, revocable guest links so reviewers can contribute without creating a full account.

The narrated walkthrough below shows the workflow. The interactive demo uses a fictional studio and keeps demo changes in your browser.

Where does feedback lose context in your workflow?