The person approving your design is rarely sitting next to you. They get whatever you can send them, and the format you choose decides what they can judge.
A screenshot can only be looked at
A screenshot has no behavior. The menu doesn't open, the button doesn't click, the form doesn't submit, and the next page doesn't exist. It also has one fixed width and one carefully captured moment of content.
That's fine when you want an opinion on how something looks. It's weak when you want to know whether the design works.
Open a mobile design on a phone. Walk the checkout. Use the navigation rather than looking at it, and let real content stretch, wrap, disappear and break things.
You can build all of that first and send a deployed preview. But then the expensive part has already happened.
If the first real test comes after the build, design feedback has already become development work.
Share what you changed
Pixy can put your edits on the real site before they exist in its code. A shared link gives someone else that same view.
They open a URL and get the site with your version applied. The data is real, the links and forms work, the navigation works, and the browser is their browser. Open it on a phone and it is the actual mobile experience, not a phone-sized rectangle on somebody else's screen.
Press the share button in the bottom bar to make one. Choose who can open it, whether it covers the current page or the whole website, which version or versions to show, and when the link should expire. The default is two hours.
Share makes the link and copies it. After that the button copies, and it turns into Save the moment you change a term, so the link already sitting in someone's inbox takes the new terms without a new URL. All shared links lists what the project has running, to edit, copy or delete, and every setting on the card is written out in Shared links.
On the other side, it's just the site
The person opening the link doesn't land in Pixy or a review tool. A plain sheet covers the page while the site loads and the edits are applied, then gets out of the way.
From there, they use the site. They can scroll, open the nav, click through pages, jump to anchors, fill in forms, and follow a flow. If you shared the whole website, the preview stays with them as they move through it in that tab.
A heading has to fit the real content. A menu has to work at the width of the reviewer's phone. A button has to make sense after the steps that lead to it. The design is no longer being reviewed as a composition. It is being used.
Put two versions in front of the same person
If you're deciding between versions, put both in the same link. More… lets you select several, and the reviewer gets a small switcher in the bottom-right corner. Main can sit beside them too.
The page and data stay in place while the design changes. Instead of asking which screenshot looks better, ask someone to complete the same task in each version.
What comes back is where they hesitated, which version made the next step obvious, and which one held up on their phone. That beats a preference between two images.
Or review it together
Turn on Live and the link becomes a shared session. Enter live and people can follow your cursor, clicks, scrolling, page changes, and edits as you make them.
They can talk through chat, microphone, or camera, raise a hand, or turn off Follow and explore on their own. Nothing is recorded. You're simply on the same site at the same time.
Live always covers the whole website. You can also schedule the session, which sends invitees a calendar entry and an email reminder. Leave takes you out while the link keeps working. End Live ends the link itself, for everyone. More is covered in Live.
Real site, limited access
The experience is real, but the access is deliberately narrow. A shared link can read the version you gave it and the images that version uses. It can't enter design mode, save changes, see other versions, or carry the preview onto another domain.
Links expire too. Two hours is the default, with the exact end time shown before you share. You can shorten it, extend it, or delete the link the moment the review is done.
Anyone with the link means exactly that, so a forwarded URL opens for whoever receives it. For private work, Invitees only ties access to named email addresses. If someone needs permanent access to the project rather than one review, that belongs in Teams.
Active links are managed from the share card, or from the Shared links block in your account.
Build the version people already used
The change is in the order. The review happens before development instead of after it.
Make the change on the real site. Send it. Let someone open it on their phone, use the real navigation, see the real data, and walk the actual flow. Fix what needs fixing while it is still a design decision.
Then build the version people already used.
Open the page you were going to screenshot and press share: your project.
Don't just look at the design. Use it.
Change something on this page, then experience it as a real page before anything gets built.