How to compare redesign directions for a feature for product managers in 2026

Steps for product managers to compare redesign directions for a feature: what to prepare, which tools to check, and mistakes to avoid.

By 2Dex · 2026-10-18

2Dex is published by the makers of SageThumbs 2K, RēDesign and VectorMagik, which are compared here alongside other tools.

Start with one screenshot of the feature as it is now, decide the design directions you want compared, and score every candidate against a fixed checklist of the feature's own requirements instead of by taste. RēDesign sends one screenshot to several AI models at the same time and shows the HTML redesigns they return in a gallery next to the original.^[1]

Option	Design directions in one run	Cost
RēDesign	Sends one screenshot to several AI models at once, each asked for a different number of variants, shown in a gallery next to the original ^[1] ^[1]	Free; you only pay the AI providers whose API keys you use ^[1]
Other redesign tools	Not published	Not published

What you need before you start

Settling on one redesign direction for a feature is easier when a few things are ready first. Work through this list before you open any tool.

A current screenshot of the feature. Capture the UI exactly as users see it today, full screen and at the real scale, so every direction starts from the same image.
A short list of the design directions to compare. These are the looks you want to see, such as a faithful refresh of the current layout, a bold reimagining of it, or a minimalist version. Naming the directions up front stops the comparison from drifting.
A fixed checklist of what must not change. Write down the feature's content, wording, behaviour and required actions, because a redesign that looks better but loses a critical step is not a candidate.
Your brand assets. Collect the logos, product photos, avatars and illustrations that belong with the feature, so a redesign can use the real marks instead of placeholders.
Your accessibility and contrast targets. Decide the level of text contrast the feature must meet, so you can check every candidate against the same standard.
The AI providers you will use. Compare these directions with a tool that works with your own provider accounts and API keys, and know what those providers charge before a run starts.
A record of the run. Keep the outputs somewhere you can hand to your team, so the chosen direction can be rebuilt.

Finally, put the checklist somewhere you can see while comparing, so every candidate is scored on the same terms.

Step by step

These steps work the same way whichever tool you pick.

Capture the feature as it is today. Take the screenshot and confirm it shows the complete UI, with no window cropped and nothing covered.
Write down what cannot change. List the content, wording and actions the feature must keep, and set the contrast level it must reach.
Name the directions to compare. Choose the looks you want to see, such as a faithful refresh, a bold reimagine and a minimalist version, and stick to that list.
Pick a tool that returns real HTML designs. A redesign you can only look at is hard to judge; one that returns working markup is easier to review and hand on.
Run the same screenshot through the same directions. Feed the one screenshot and the named directions into the tool so every candidate starts from the same image and brief.
Compare the outputs side by side. Look at the redesigns next to the original screenshot, not one at a time, so differences between directions are visible.
Hide which model made which design. Judging a redesign without knowing its source keeps the score on the design, not the reputation of the model behind it.
Score every candidate against your fixed checklist. Work through the same items in the same order for each candidate, and mark a pass or fail for each instead of an overall feeling.
Check the contrast of the text in each redesign. Verify that the body text and labels in each candidate meet your stated accessibility level.
Look for your real brand assets. Confirm the logos, photos and illustrations inside each redesign are yours, not filler images.
Pick one direction. Take the candidate that passes the checklist, not the one that looks the most striking at first glance.
Hand the chosen direction to your team with its record. Pass along the run, the picked design and a description of how the look was built, so it can be rebuilt without another round of guessing.

Tools that can do it

Facts are published here for only one tool, so the comparison is short. For any other option, such as another AI design tool that returns redesigns from a screenshot, check its own page for which AI models it works with, what it returns, how it handles your brand assets and what its output can be handed to your team.

### RēDesign

RēDesign is made by the team that publishes this site. It sends one UI screenshot to several AI models at the same time and shows the HTML redesigns they return in a gallery next to the original.^[1] In one run you can ask each model for a different number of variants.^[1] It comes with prompt presets such as faithful refresh, bold reimagine and minimalist, and you can also write your own prompts.^[1] It shows you two outputs with the model names hidden, and each pick you make updates a ranking of the models.^[1]

For product managers, a few other behaviours matter. With one click it checks an output's text contrast against WCAG AA, using the rendered pixels.^[1] It locates and crops logos, product photos, avatars and illustrations so redesigns can embed the real brand marks.^[1] It checks each saved redesign on your machine against a fixed list of generic AI styling patterns and shows the findings as a badge on the card.^[1] You can download a whole run as a zip, or download a DESIGN.md file for the redesign you picked so a coding agent can rebuild that look.^[1]

On running and cost, RēDesign is free, and you only pay the AI providers whose API keys you use.^[1] It shows an estimated cost before you start a run and tracks what each run costs.^[1] It works out which provider each pasted API key belongs to and rotates through several keys per provider, pausing keys that keep failing.^[1] You can line up several batches, start them together and drag waiting batches to change their order.^[1] Everything in the app can also be done from the command line, and an AI agent can control it too.^[1] The packaged app is for Windows only; running from source works on Windows, macOS or Linux with Bun 1.2 or newer.^[1] On Windows you download redesign-windows-x64.exe from GitHub Releases.^[1]

Common mistakes to avoid

Deciding by taste instead of a checklist. A direction that looks striking can still fail the feature's requirements. Score every candidate against the same fixed list.
Comparing one direction at a time. Judging candidates one after another makes differences hard to see. Compare the redesigns side by side, next to the original.
Judging before hiding the sources. Seeing which model made which design can tilt the score. Judge candidate designs with the model names out of sight first.
Skipping the contrast check. A redesign that fails the feature's accessibility level is not shippable, whatever it looks like.
Leaving in placeholder images. Redesigns that show fake logos or stock photos hide how the real brand marks will look. Check that the real assets appear.
Comparing directions in separate runs. Feeding the same screenshot and directions into one run keeps every candidate on the same brief; separate runs drift out of step.
Throwing the run away. Without a record of the chosen redesign, the team cannot rebuild the look. Keep the run and the picked design.
Choosing AI providers without their cost. The provider bills each run, so know what it will charge before you start, not after.

Frequently asked questions

How can product managers compare redesign directions for a feature?

Start from one screenshot of the feature as it is today, name the design directions to compare, and score every candidate against a fixed checklist of the feature's requirements and contrast targets. Looking at the redesigns side by side with the sources hidden keeps the score on the design itself. Pick the candidate that passes the checklist, then hand it to the team with a record of how it was built.

Can RēDesign compare several design directions in one run?

Yes. RēDesign sends one UI screenshot to several AI models at the same time and shows the HTML redesigns they return in a gallery next to the original.^[1] In that same run you can ask each model for a different number of variants.^[1] This keeps every candidate on the same screenshot and brief, which makes the comparison fair.

Does RēDesign cost anything?

RēDesign is free, and you only pay the AI providers whose API keys you use.^[1] It shows an estimated cost before you start a run and tracks what each run costs.^[1] Because the providers bill for each run, set up your own accounts and keys first, and check what the providers charge before you start comparing.

Does RēDesign show which model made each redesign?

RēDesign shows you two outputs with the model names hidden, and each pick you make updates a ranking of the models.^[1] That lets you judge the designs on their own merits rather than on the reputation of the model behind them, and the ranking built up from your picks shows how the models compare with each other. ^[1]

Can RēDesign hand a chosen redesign to the engineering team?

Yes. You can download a whole run as a zip, or download a DESIGN.md file for the redesign you picked so a coding agent can rebuild that look.^[1] Because the outputs are HTML redesigns, the chosen direction can be handed on with its build description, which keeps the redesign from being lost in the handover.

RēDesign is free; you only pay the AI providers whose API keys you use. ^[1]

Try RēDesign

Sources

RēDesign's own description of itself (the product of this site's publisher)