Hey Sumolings – we’ve just released Pixefy v1.2.0, and this was a big development week for us.

We listened closely to your feedback, fixed a lot of issues, and added several improvements to make website testing easier and more clear.

The biggest new addition is our Console Error & Warning Monitor for Pro users. Instead of opening DevTools separately, you can now see console errors, warnings, and even network issues directly inside Pixefy for each pane.

We also introduced:

• Resize Ruler for easier breakpoint checking while resizing panes
• Performance Metrics on pane headers, so you can quickly spot load time and layout shift info
• Show / Hide controls for toolbar, ruler, and metrics
• Update check and restart option in the What’s New popup

We also made a lot of improvements behind the scenes and of course, we fixed many reported issues across panes, sync, screenshots, menus, iframe behavior, and overall stability. -> Full changelog

Big thanks again to everyone who shared feedback, reported bugs, and helped us improve Pixefy – it really makes a difference.

Hey Sumolings – thank you so much for the interest in Pixefy. We’re seeing some early traction, and right now we’re focused on helping everyone get onboarded as quickly as possible.

A quick product update from our side (v1.1.0):

• we’ve started rolling out mockups in Pixefy, and we’ll keep adding more over time
• fixed a number of issues, including some reported by this community – thank you
• Firefox extension issues are now fixed

We also have a YouTube channel with tutorials if you want to get up to speed faster -> @Pixefy-io

Quick links to common questions:

• How user agents work: https://www.youtube.com/watch?v=yhmSOLxarmc
• It does not load my website: https://www.youtube.com/watch?v=5DDX4dt67dY

Next on the roadmap, we’re working on user management, so you’ll be able to manage invited users and team status more flexibly within your tier limits.

We’re also getting lots of questions about Safari, Opera, Brave, and other browsers. Right now, we officially support Chrome and Firefox, but support for more Chromium-based browsers is definitely on our roadmap.

Thanks again for all the feedback, bug reports, and support – it’s helping us improve Pixefy fast.

We built Pixefy because reviewing websites across screen sizes still takes more effort than it should.

For something that is such a basic part of shipping web projects, the workflow is still surprisingly scattered. Teams jump between browser resizing, device switching, manual comparisons, inspection tools, screenshots, and notes just to understand how a site behaves across breakpoints.

It is possible to do all of that manually. It is just not efficient. That is why we built Pixefy.

Pixefy helps teams review responsive websites in a more visual and connected way. Instead of constantly jumping between tools and tabs, you can preview multiple screen sizes in one place, compare layouts side by side, inspect UI details, review SEO basics, test dark mode, and keep track of changes as you go.

The goal was not to create another utility with random features packed in. We wanted to build something that supports the actual workflow of reviewing and improving websites before launch.

• For designers, Pixefy makes it easier to catch layout shifts, spacing issues, and visual inconsistencies.
• For developers, it helps validate responsive behavior faster and inspect issues with more context.
• For QA teams, it creates a clearer way to review screens, track changes, and share feedback.
• For agencies, it can make client review and internal collaboration much less messy.

What makes Pixefy different is that it is built around the real process of responsive review, not just one isolated step in it.

• For solo makers, it can make website review feel much lighter.
• For product teams, it can improve handoff and reduce repeated checks.
• For agencies, it can bring more structure to responsive feedback.

That is the idea behind Pixefy: helping teams review websites with less friction and more clarity.