--- title: InVision Reviews meta_title: 'InVision Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 684 reviews by the users' company size, role or industry to find out how InVision works for a business like yours. aggregate_rating: rating_value: 4.4 review_count: 684 scale: '5' date_modified: '2026-07-07' parent_category: name: Software Design url: https://www.g2.com/categories/software-design --- # InVision Reviews **Vendor:** InVision **Category:** [Prototyping Software](https://www.g2.com/categories/prototyping) **Average Rating:** 4.4/5.0 **Total Reviews:** 684 ## About InVision InVision is the visual collaboration platform powering the world’s smartest companies. We exist to make every kind of work more collaborative, inclusive and impactful. Between our platform, our practices, and our community, we enable tens of thousands of organizations to improve their processes and workflows so they can get the most out of their most valuable asset: their people. Sign up for a free trial at invisionapp.com and begin streamlining your digital product workflow. ## InVision Pros & Cons **What users like:** - Users love the **animation tools** in InVision, enabling seamless transitions and vibrant mood boards with real-time collaboration. (1 reviews) - Users enjoy the **seamless design process** in InVision, making collaboration and code generation efficient and intuitive. (1 reviews) - Users love the **collaboration tools** in InVision, enabling seamless feedback and vibrant teamwork on creative projects. (1 reviews) - Users love the **creativity features** of InVision, enabling vibrant collaboration and seamless design iteration. (1 reviews) - Users highlight the **ease of use** in InVision, facilitating smooth collaboration and efficient design processes. (1 reviews) - Features (1 reviews) - Prototyping (1 reviews) - Real-time Collaboration (1 reviews) - Sharing (1 reviews) - Smooth Performance (1 reviews) **What users dislike:** - Users find **comment management problematic** as scattered threads make it difficult to follow conversations and maintain context. (1 reviews) - Users struggle with **commenting difficulty** as scattered threads make it hard to follow and manage conversations effectively. (1 reviews) - Users struggle with **comment management** , often losing context as threads become overwhelming and scattered. (1 reviews) - Users struggle with **poor organization** in comment management, losing track of conversations and context easily. (1 reviews) ## InVision Reviews ### 1. InVision Made Prototype Sharing and Feedback Effortless **Rating:** 4.0/5.0 stars **Reviewed by:** Luca P. | Chief Operations Officer DEQUA Studio | Formerly CTO in MarTech, Marketing and Advertising, Mid-Market (51-1000 emp.) **Reviewed Date:** June 05, 2026 **What do you like best about InVision?** The company discontinued its design collaboration services, prototypes, Inspect, DSM, boards and the rest, on December 31, 2024, and everything stored in an account was deleted at the end of that day. Freehand, the visual whiteboard piece, had already been sold to Miro in 2023. So none of what follows is something you can sign up for and try today. It is an account of what the tool did well across the years my teams actually ran on it, written while the memory of using it daily is still close. The prototype sharing link was the thing that made InVision matter, and it is the thing I missed first once it was gone. The workflow was simple in a way that is easy to undervalue now that everyone expects it. I uploaded a set of static screens, wired them together with hotspots, and got a single URL I could send to a client or a product owner. They clicked through the flow on their own machine, on their own time, no software to install and no account hoops in the early days. Before this existed, showing a flow meant a screen share on a call, or a folder of flat PNGs with arrows drawn on them, or worse, a slide deck pretending to be an interactive product. InVision turned a pile of artboards into something a non-designer could navigate and reason about, and that one capability reset how stakeholders expected to receive design work. Craft Sync was the piece that made the prototype side bearable to maintain. I worked primarily in Sketch for most of the InVision years, and the Craft plugin pushed selected artboards straight into an InVision project without an export step. Save in Sketch, sync, and the screens updated in the prototype. The alternative, which I lived through before Craft matured, was exporting images by hand and re-uploading them every time a screen changed, which is exactly the kind of friction that quietly kills a tool inside a team. With Sync, keeping a prototype current stopped being a chore I dreaded and became a button I pressed without thinking. It was not flawless, syncing over a slow connection at a client site could be genuinely painful, but on a normal day it did its job. Contextual comments pinned to the screen were where InVision earned its keep on the collaboration side. A reviewer did not have to describe where the problem was, they clicked the spot and left the note right there. When I shared a flow with five stakeholders across three time zones, the feedback came back attached to the exact pixel it referred to, instead of arriving as a paragraph in an email that I then had to translate into a location on a screen. That single behavior collapsed a whole category of back-and-forth. I could open a screen, see every comment threaded against it, mark them resolved as I worked through them, and have a clean audit trail of what was raised and what was addressed. For client work especially, that record mattered as much as the feedback itself. Inspect was the developer handoff feature, and it was the part that justified the subscription line item to people who were not designers. Once a prototype was synced with assets marked for export in Sketch, a developer opened Inspect mode and pulled dimensions, hex codes, font details, spacing and downloadable assets straight from the screen. No redline document, no designer sitting next to a developer reading off measurements, no Slack thread asking what shade of grey that divider was. The developer self-served the spec. On teams where design and engineering sat in different rooms or different companies, Inspect removed a daily source of interruption for me and a daily source of guesswork for them. It also slotted into a Jira workflow, so a prototype with Inspect enabled could hang off the ticket the developer was already looking at. The integration posture in general was a strength while it lasted. InVision positioned itself as the collaborative layer on top of whatever design tool you actually drew in, Sketch first and most deeply, but it accepted uploads from Photoshop and Adobe XD too, and later connected to the Jira and Confluence stacks teams already lived in. The pitch was that you did not have to abandon your drawing tool to get collaboration, prototyping and handoff in one place, and for a good stretch that pitch held. It meant I could standardize a team on InVision for the shared layer without forcing everyone onto one design application. DSM, the Design System Manager, was the ambitious part, and when it worked it was genuinely useful for keeping a team consistent. The idea was a living library of components, colors and text styles that designers pulled from and that stayed connected back to the source. On larger projects, having a single place that defined what a button or a type ramp actually was, rather than every designer reinventing it per file, cut down the slow drift that turns a tidy design system into a mess six months in. I will be honest about its limits in the next section, but the intent was right and the basic version of it saved real rework. Ease of onboarding for non-designers deserves a specific mention, because it is the reason InVision spread inside organizations rather than staying a designer tool. I handed prototype links to executives, marketers and clients who had never touched a design tool, and they figured out clicking through a flow and leaving a comment within a minute or two. There was nothing to learn. That low barrier is why a design team could pull the whole company into the review process instead of presenting to it, and pulling people in is almost always the better outcome. **What do you dislike about InVision?** The bigger structural problem was that InVision was never the place you actually designed. It sat on top of Sketch or Photoshop or XD, which was the whole pitch, but it also meant the moment a single tool could do design, prototyping and handoff in one canvas, the multi-tool dance InVision required started to look like overhead rather than a workflow. When Figma arrived with real-time design and prototyping in one browser tab, the question stopped being which features InVision had and became why I was round-tripping between two tools at all. InVision's answer to that was too slow in coming and never convincing. Cost was a recurring sore point, particularly for smaller teams and independent practitioners. The pricing added up quickly once you were past the most basic usage, and there was a real sense of being nickel-and-dimed, including charges that gated archived projects. For a freelancer or a small studio watching every subscription, InVision sat in the bracket where you regularly asked whether it was worth it, and toward the end the answer kept tilting toward no. **What problems is InVision solving and how is that benefiting you?** The central problem it solved was getting interactive design in front of people who were not in the room. Before InVision, sharing a flow with a client or a stakeholder meant a meeting, a screen share and a lot of narration, or a set of flat exports that asked the viewer to imagine the interaction. The shareable prototype link replaced all of that. I sent a URL, the recipient clicked through the actual flow on their own schedule, and the conversation started from a shared, concrete reference instead of from my description of one. The benefit was less coordination, fewer meetings that existed only to show something, and stakeholders who understood what they were approving because they had navigated it themselves. It solved the feedback-translation problem, which was a quiet daily tax I did not fully appreciate until it was handled. Comments pinned to the exact spot on a screen meant I no longer had to decode a vague written note and guess which element it referred to. The before-state was an inbox of feedback I had to reconcile against the design by hand. The after-state was every note sitting on the pixel it concerned, threaded, resolvable, and traceable. For client work that audit trail of what was raised and what was fixed was worth as much as the speed. It solved design-to-development handoff in a way that removed me from the loop. Inspect let developers pull measurements, colors, fonts and assets directly off the synced screens without asking me anything. Before that, handoff meant building redline documents, or sitting with a developer reading specs aloud, or answering a steady trickle of "what is this value" questions all sprint. With Inspect, the developer self-served and I got my focus back. On teams split across companies or time zones, that self-service was the difference between handoff being a bottleneck and handoff being a non-event. It solved the consistency-drift problem on larger efforts, at least partially, through DSM. Keeping every designer pulling from one defined library of components and styles, rather than each person rebuilding a button slightly differently, slowed the gradual decay that turns a coherent design language into a pile of near-duplicates. The benefit showed up months later, in the rework that did not have to happen because the system had held together. And it solved a cultural problem more than a technical one: it pulled non-designers into the design process. Because a prototype link required nothing to use, I could invite the whole organization to navigate and comment instead of presenting to a passive audience. Marketing, product and leadership engaged with the actual flow early, which surfaced misunderstandings while they were still cheap to fix. That habit of broad, early, hands-on review is the thing I carried forward to whatever tool came next, and it is probably InVision's most durable legacy in how I work. The tool is gone, but the expectations it set for what good design collaboration feels like outlived it. ### 2. Good for Early Wireframes, but Little Value Once Figma Covers It All **Rating:** 2.5/5.0 stars **Reviewed by:** Ganapathi K. | Associate Product Manager, Small-Business (50 or fewer emp.) **Reviewed Date:** April 28, 2026 **What do you like best about InVision?** It’s a good prototyping and wireframing mockup tool, and it’s easy to share visual mockups of user flows. I can share multiple screens with non-technical business users, which helps me quickly show what the UX flow looks like. **What do you dislike about InVision?** It’s pretty much out of the game for us. We used this in the early stages of our development, but later on Figma itself had all of these features, along with the actual UI development and collaboration tools. Because of that, the value add ended up being almost nothing. We ultimately switched to using Figma for prototyping and for mock wireframing. It got outdated in it's features, we stopped using it last few years **What problems is InVision solving and how is that benefiting you?** It partially solved us the problem of showing the user flows to different stakeholders with internactions and the prototype version to take the call on weather or not to go with a specific flow. ### 3. Still a good product even with new competitors in the market **Rating:** 3.0/5.0 stars **Reviewed by:** Joe M. | CEO, Hospital & Health Care, Small-Business (50 or fewer emp.) **Reviewed Date:** May 22, 2026 **What do you like best about InVision?** Using the freehand... probably not the most common answer but I've used for a while and works just as needed. **What do you dislike about InVision?** The prototyping is still good but newer tools are offering more capabilities and easier to use. Like Figma. **What problems is InVision solving and how is that benefiting you?** white boarding. Again there are newer tools but this works just as good ### 4. Very handy tool to make prototype live **Rating:** 5.0/5.0 stars **Reviewed by:** Maria S. | UX Designer/Researcher, Mid-Market (51-1000 emp.) **Reviewed Date:** March 14, 2024 **What do you like best about InVision?** Intuitive, very easy to use, you don't need any special skills **What do you dislike about InVision?** It doesn't really understand buttons or links on your prototypes, and you can highlight only spots on the picture—for test users, this might create confusion. **What problems is InVision solving and how is that benefiting you?** It helps to show how the future application or website works. I don't have to describe it to the client or my team—just make a demo. ### 5. Invision works for what it is **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Design | Small-Business (50 or fewer emp.) **Reviewed Date:** March 24, 2022 **What do you like best about InVision?** It's really easy to use and hand off to clients for review. I can't send Figma prototypes because they're too big, so these tend to work great since they are just images. **What do you dislike about InVision?** Sometimes it can be such a hassle trying to upload and update screens. The idea of matching naming conventions and screen overwriting eachother can be daunting at first. **Recommendations to others considering InVision:** Make sure your file names are very clear and precise **What problems is InVision solving and how is that benefiting you?** As stated - we typically use Figma, but sometime Figma files are too large for clients to open when their computers aren't as fast as ours. Invision works great for quick reviews. ### 6. Daily InVision User **Rating:** 4.5/5.0 stars **Reviewed by:** Matthew M. | Mid-Market (51-1000 emp.) **Reviewed Date:** August 14, 2023 **What do you like best about InVision?** Overall InVision works great for most of our clients. I love that fact that we can share the whole design and make links to other pages to give the Client a better user experience while in the protoyping phase. **What do you dislike about InVision?** One of the biggest downsides about InVision is that the client can't copy the content on the protype to make edits. We have asked many times when will this happen but yet to see this feature added. Clients then have to add comments like " before the word ... add ... then after the word... add... This can make thins extremely confusing for both parties. **What problems is InVision solving and how is that benefiting you?** There solving the visually and content side of the protype before the design moves into devleopment. We have multiple phases we walk them through to get us close to 100% approval before adding the functionality. ### 7. InVision is good but figma & adobe Xd gives you more power **Rating:** 3.0/5.0 stars **Reviewed by:** Rahul K. | UI/UX Designer , Mid-Market (51-1000 emp.) **Reviewed Date:** February 28, 2024 **What do you like best about InVision?** Learning curve is easy, and online platform give accessiblity at any point of time. **What do you dislike about InVision?** Prototype and presentation via tool is not that convenient **What problems is InVision solving and how is that benefiting you?** Product design for startup with budget constraints is helping alot. ### 8. Invision is an amazing software **Rating:** 5.0/5.0 stars **Reviewed by:** Ahtisham A. | Product Designer, Small-Business (50 or fewer emp.) **Reviewed Date:** November 07, 2023 **What do you like best about InVision?** Flexibale and easy to use.I have frequency of use for wireframing. Invison ease my implimention in design and also ease of integration as well. There cusytomer support is pretty nice and easy. **What do you dislike about InVision?** Some time it is complex to design components and less Number of Features in the software. **What problems is InVision solving and how is that benefiting you?** It helps me to create wireframe and to set the flow also it helps the client to understand the basic journey of design so he can under what he wants in the sofwatre or app. ### 9. Using InVision has been instrumental in streamlining my design collaboration process. **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Graphic Design | Small-Business (50 or fewer emp.) **Reviewed Date:** August 08, 2023 **What do you like best about InVision?** what I like best is its seamless platform for creating interactive prototypes and collaborating with team members. The ability to visualize and present design concepts effectively, gather feedback, and iterate swiftly enhances the overall design process and communication within the team. **What do you dislike about InVision?** I might find that some aspects I dislike include occasional performance issues when working on complex projects, and potentially a learning curve for newcomers to the platform. However, these downsides are outweighed by the overall benefits of efficient collaboration and prototype creation that InVision offers. **What problems is InVision solving and how is that benefiting you?** the platform effectively addresses the challenge of visualizing and presenting design concepts to stakeholders and clients. By allowing me to create interactive prototypes with transitions and animations, InVision enables me to convey the user experience effectively, gather feedback, and make informed design decisions. This benefits me by streamlining the design iteration process, reducing misunderstandings, and ensuring that the final product aligns with the intended vision. ### 10. What an amazing tool for Mockups and Wireframes **Rating:** 4.0/5.0 stars **Reviewed by:** Arpi J. | Solution Consultant, Mid-Market (51-1000 emp.) **Reviewed Date:** June 23, 2023 **What do you like best about InVision?** I am in awe of this tool ever since I have used it. We have used this tool to create design mockups and also the suggestive wireframes for discussions with client **What do you dislike about InVision?** I practically don't have anything to dislike about this tool at all. Only suggestion is if there would be a few OOTB design template to start from so that you dont have to start from scratch. **What problems is InVision solving and how is that benefiting you?** We have created a lot of project wireframes for our discussions with clients and we change them on the fly easily. We also create mockups to be shared with devs for further development which are designed easily in InVision ## InVision Discussions - [Trading](https://www.g2.com/discussions/29793-trading) - 1 comment, 1 upvote - [What are the most helpful InVision integrations?](https://www.g2.com/discussions/27595-what-are-the-most-helpful-invision-integrations) - 1 comment, 1 upvote - [What advice do you have for someone just starting to use InVision?](https://www.g2.com/discussions/27585-what-advice-do-you-have-for-someone-just-starting-to-use-invision) - 1 comment, 1 upvote - [What’s something you wish InVision could do that it currently can’t?](https://www.g2.com/discussions/27580-what-s-something-you-wish-invision-could-do-that-it-currently-can-t) - 1 comment, 1 upvote - [What are some other use cases for InVision?](https://www.g2.com/discussions/27575-what-are-some-other-use-cases-for-invision) - 1 comment, 1 upvote - [View InVision pricing details and edition comparison](https://www.g2.com/products/invision/reviews/invision-review-593153?section=pricing&secure%5Bexpires_at%5D=2026-07-07+17%3A21%3A31+-0500&secure%5Bsession_id%5D=43774947-0a33-4474-a818-551818d6b976&secure%5Btoken%5D=11ae0054f93de290b0ef2a84aaab41b56474c68bd9bd8d6602dfdb59f1e19831&format=llm_user) ## InVision Integrations - [Sketch](https://www.g2.com/products/sketch/reviews) ## InVision Features **Performance Tracking** - Dashboard - Asset Performance - Template Usage **Platform Basics** - Modeling Tools - Feedback and Communication - Framework Libraries - Editing Tools **Platform Basics** - Importing Abilities - Content Design Tools - Framework Libraries - Outlining Tools - Mockup Creations **Platform Basics** - Mockup Creations - Outlining Tools - Import Graphic Design Tools - Feedback Communication - Content Libraries - Export Wireframes and Prototypes **Platform Basics - Software Design Platforms** - User Interface Testing - Presentation Integrations - Error Documentation - Sharing Components **Functionality** - Design Templates - Workflow Management - Collaboration - Educational Resources **Platform Additional Functionality** - Sharing Components - Error Documentation - User Interface Testing - Presentation Integrations **Platform Additional Functionality** - Collaboration Software Integration - Feedback Communication - Exporting Capabilities **Platform Additional Functionality** - Design and Editing Tools - Collaboration Capabilities - Diagramming and Collaborative Whiteboard Integrations - Documenting Trial Errors **Platform Additional Functionality - Software Design Platforms** - Editing Tools - Framework Libraries - Feedback and Communication - Modeling Tools **Agentic AI - Prototyping** - Autonomous Task Execution - Multi-step Planning - Cross-system Integration - Natural Language Interaction - Proactive Assistance ## Top InVision Alternatives - [UXPin](https://www.g2.com/products/uxpin/reviews) - 4.2/5.0 (116 reviews) - [Figma](https://www.g2.com/products/figma/reviews) - 4.7/5.0 (1,543 reviews) - [Sketch](https://www.g2.com/products/sketch/reviews) - 4.5/5.0 (1,209 reviews)