RankDude

Test log

UXMagic test data

Raw results for the UXMagic review. The verdict is in the review.

Tested
7 November 2026
Tester
Miles Foster
Account
Free demo account, signed up by RankDude, nothing paid to the brand
Tests
9
Screenshots
8
Environment
Google Chrome on desktop

Results

IDTestKey measurementScore
T01Brand Kit & Consistency–n/a
T02Sharing & Collaboration–n/a
T03Brief to First DraftApproved plan to finished draft: About 90 seconds5/5
T04Brief AdherenceRequired elements right: 39 of 403/5
T05First Draft QualityDesign faults: 73/5
T06Editing FreedomEdits that worked: 5 of 122/5
T07Export & HandoffPoints that worked: 4 of 102/5
T08Rights & Commercial UseOutput ownership stated: No2/5
T09Pricing & ValuePro, paid yearly, a year: $2103/5
Overall (in the review)3.5/5
T01

Brand Kit & Consistency

n/aNot Tested
Method
Upload logo, fonts and colours as a brand kit, then generate ten designs and check them.
Remark
Not graded; left out of the average.
Raw notes

Upload logo, fonts and colours as a brand kit, then generate ten designs and check them.

Not run: ten generations do not fit a day of 20 credits, and the two briefs I ran used all of it. The tool has a Style Guide option on the prompt box, which was filled from the brief automatically.

  • Needs a paid month or several days.
T02

Sharing & Collaboration

n/aNot Tested
Method
Eight points tried with a second account.
Remark
Not graded; left out of the average.
Raw notes

Eight points tried with a second account.

Not run: no second account was made. The Share dialog offers Private or Anyone with the link, which lets people view, and the preview has a Share button.

  • Needs a second test account.
T03

Brief to First Draft

5/5Tested
Method
Each brief was typed into the dashboard prompt box with its logo and photo attached.
Approved plan to finished draft
About 90 seconds
Credits for the landing brief
4 of 20
Credits for the app brief
16 of 20
Remark
Scale 5: median under 5 minutes. Two briefs ran, and both finished in about 90 seconds.
Raw notes

Each brief was typed into the dashboard prompt box with its logo and photo attached. The tool first proposes a screen plan, which I approved at once; the clock ran from sending the brief to the last screen being finished.

The landing page was finished about 90 seconds after I approved its screen plan, with one screen of 1440 by 2045 pixels. The counter went from 20 to 16 credits.

The five-screen app was finished about 90 seconds after I sent it, and under a minute after I approved its plan, with five screens of 390 by 844 pixels. The counter went from 16 to 0 credits.

In both runs the first thing on screen was a blue placeholder frame, then the finished screens appeared. The screen-plan step took about a minute in the landing run because I approved it late; I approved the app plan 40 seconds in.

  • Times come from screenshots saved every 10 seconds and the screen recording, so they are good to about 10 seconds.
T04

Brief Adherence

3/5Tested
Method
The 20 required elements of each brief were read from the design's own HTML (text, font, colour and size of every element) before any edit, and the five screens' labels gave their sizes.
Required elements right
39 of 40
Invented lines
More than 30
Remark
Scale 3: the scale gives 5 for 58 or more of 60 right with nothing invented, and 3 for two or three invented items. Here the count is 39 of 40 (scaled, 58 of 60) but the invented lines are far beyond three, none of them prices, reviews or photos, so I graded 3.

UXMagic: The top of the landing page draft exported as a PNG: header with the supplied logo and a hero with the supplied yarn photo.

UXMagic: The top of the landing page draft exported as a PNG: header with the supplied logo and a hero with the supplied yarn photo.
T04-1 The top of the landing draft as exported: the supplied logo and yarn photo are in place, with an extra label above the headline.
Raw notes

The 20 required elements of each brief were read from the design's own HTML (text, font, colour and size of every element) before any edit, and the five screens' labels gave their sizes.

39 of 40 were right. The landing page got 19 of 20: every headline, line, price, link, address and hours matched word for word, the colours and the Fraunces and Inter fonts were used, the supplied logo is top left and the supplied yarn photo is in the hero. The one miss is supporting text, which uses a lighter brown, #6B5A51, instead of bark #3B2F2A. The app got 20 of 20.

A lot of text I did not supply was added: about 15 lines on the landing page (small labels, a line under each product, an Add a skein button on each card, a Save your seat button, a footer tagline) and about 20 on the app (labels above every title, a rewritten title on the session screen, descriptions such as just the two of you, a month shown as October 2025, example names and an example email). No prices, reviews or stock photos were invented.

  • Two briefs, scaled to 60 elements. The draft in the picture is the exported file, which carries my one-word edit (calm for slow).
T05

First Draft Quality

3/5Tested
Method
Both drafts were opened at their own size and the landing page also at 768 and 390 pixels.
Design faults
7
Text failing contrast on the landing page
0
Remark
Scale 3: 6 to 10 faults.

UXMagic: The app's Welcome screen: the dark title and text on a dark green overlay with the studio photo barely visible.

UXMagic: The app's Welcome screen: the dark title and text on a dark green overlay with the studio photo barely visible.
T05-1 The Welcome screen: dark text on a dark overlay, about 2 to 1.

UXMagic: The landing page at 390 pixels: the logo runs into the Shop link and Classes is cut at the edge.

UXMagic: The landing page at 390 pixels: the logo runs into the Shop link and Classes is cut at the edge.
T05-2 At 390 pixels the nav runs into the logo and Visit is off the edge.
Raw notes

Both drafts were opened at their own size and the landing page also at 768 and 390 pixels. Contrast was calculated from the real colours, and tap targets were measured.

Seven faults. Text contrast passed on every element of the landing page and the app's other four screens. The faults: (1) the nav links Shop, Classes and Visit are 20 pixels tall; (2) the Find us on Orchard Row link is 20 pixels tall; (3) at 390 pixels the nav runs into the logo and Visit is pushed off the right edge; (4) the three product cards show flat coloured circles instead of products; (5) on the app's Welcome screen the dark ink title and text sit on a dark pine overlay at about 2 to 1 contrast; (6) the supplied studio photo is almost invisible under that overlay; (7) the calendar days are 36 pixels tall.

Everything else held: a clear title and body order on every screen, no cut-off text at the required sizes, and the Welcome button and form fields are 48 pixels tall.

  • The app screens are fixed phone frames, so the 360 and 768 pixel checks were done on the landing page only.
T06

Editing Freedom

2/5Tested
Method
Twelve fixed edits on the landing page in Edit Mode.
Edits that worked
5 of 12
Edit Mode AI calls
None needed
Remark
Scale 2: 4 to 6.

UXMagic: UXMagic's properties panel for an image: Replace Image, inner padding, flip and alt text, with no crop control.

UXMagic: UXMagic's properties panel for an image: Replace Image, inner padding, flip and alt text, with no crop control.
T06-1 The image panel: replace, padding and flip, no crop.
Raw notes

Twelve fixed edits on the landing page in Edit Mode. An edit counts when it did what was asked with a normal control and no workaround.

Five worked: an element was moved by hand (by dragging its layer in the layers panel, because dragging on the canvas did nothing), a text box was resized from 512 to 360 pixels, one word was changed in place (I retyped the heading with slow changed to calm), the whole page was made 768 pixels wide and its layout reflowed, and three undo steps put back an image swap, a resize and a reorder.

Seven did not. There is no way to select more than one element, so a font or colour cannot be changed across the design in one go and three elements cannot be aligned with each other. A new image can be swapped in, but there is no crop control, only inner padding and flip. I found no lock control and no control that adds a section without a written prompt. The twelfth edit, a written instruction, could not be run because the credits were at zero.

  • The written-instruction edit may work with credits; it was not run. Edit Mode itself costs no credits.
T07

Export & Handoff

2/5Tested
Method
Ten export points tried on the landing page: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma, HTML code that runs on a plain host, fonts named, full resolution, bulk export, no watermark and export of the source assets I uploaded.
Points that worked
4 of 10
PNG size
2880 by 4090
Remark
Scale 2: 3 to 5.

UXMagic: UXMagic's Bulk Export menu: Export to Figma, Export to React with a 2 credit tag, Download as HTML/CSS/JS and Connect GitHub.

UXMagic: UXMagic's Bulk Export menu: Export to Figma, Export to React with a 2 credit tag, Download as HTML/CSS/JS and Connect GitHub.
T07-1 The Bulk Export menu; React costs 2 credits.

UXMagic: UXMagic's Upgrade required message when downloading the ZIP export on the free plan.

UXMagic: UXMagic's Upgrade required message when downloading the ZIP export on the free plan.
T07-2 The ZIP export on the free plan: Upgrade required.
Raw notes

Ten export points tried on the landing page: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma, HTML code that runs on a plain host, fonts named, full resolution, bulk export, no watermark and export of the source assets I uploaded.

Four of ten worked. The HTML download is a 16 KB file that renders at the same 2045 pixel height with Fraunces and Inter loaded; it names both fonts; the PNG is 2880 by 4090 pixels, sharp, and carries no watermark.

Six did not. The PNG is twice the brief size (2880 pixels wide, not 1440). The image menu offers PNG, JPEG and WebP, with no SVG. The PDF option is greyed out. The all-screens ZIP shows Upgrade required, and React export costs 2 credits. The HTML links to my uploaded logo and photo on UXMagic's own storage and to scripts on public CDNs, so the assets are not exported. Copy to Figma finished, but I did not paste it into Figma, so I did not count it.

  • Figma, React and the ZIP were not fully tried; see the testing limits.
T08

Rights & Commercial Use

2/5Tested
Method
I read the Terms of Use (last modified 23 February 2026) and the Privacy Policy, reached from the links in the site footer, and looked for ownership, commercial use, model training and an indemnity.
Output ownership stated
No
Refunds
None
Remark
Scale 2: terms unclear on ownership or training.

UXMagic: UXMagic's terms of use showing the Refunds Policy, Links to other websites and Modification sections.

UXMagic: UXMagic's terms of use showing the Refunds Policy, Links to other websites and Modification sections.
T08-1 The terms: refunds are not offered, and nothing on who owns the output.
Raw notes

I read the Terms of Use (last modified 23 February 2026) and the Privacy Policy, reached from the links in the site footer, and looked for ownership, commercial use, model training and an indemnity.

The terms say nothing about who owns what you generate, whether the output can be used commercially, whether your briefs or files are used to train models, or whether UXMagic protects you if generated content causes a claim. The privacy policy covers personal data, sharing with service providers and your rights, and does not mention model training either.

What the terms do say: accounts are for one user, UXMagic can end your access at any time without notice, and "We currently do not offer refunds on subscriptions or credit purchases."

  • No lawyer's reading; only the two pages above. A silent contract is not a promise either way.
T09

Pricing & Value

3/5Tested
Method
Plans were read on the public pricing page in both billing views, and the credit allowance was read in the product.
Pro, paid yearly, a year
$210
Pro, paid monthly
$35 a month
Remark
Scale 3: $200 to $299 a year.

UXMagic: UXMagic's pricing page with the Free, UX Magic Pro and Enterprise plans in the yearly view.

UXMagic: UXMagic's pricing page with the Free, UX Magic Pro and Enterprise plans in the yearly view.
T09-1 The plans in the yearly view, read on 12 November 2026.
Raw notes

Plans were read on the public pricing page in both billing views, and the credit allowance was read in the product.

The one paid plan is UX Magic Pro: $35 a month, or $17.50 a month paid yearly, about $210 a year. It gives 2400 credits a month, up to 400 screens, unlimited projects and 250 Figma exports. Enterprise is priced on request.

Free gives 20 credits a day, up to 3 screens a day, 5 projects and 1 Figma export. The two briefs I ran used all 20 credits of one day. No refunds are offered.

  • No plan was bought; renewal prices were not seen. The terms do not say whether commercial use is allowed on free or Pro.

Other features checked

Coverage

Tested

  • The Pinecone & Thread landing brief and the Lumen & Pine booking app brief, each with its logo and photo attached
  • Forty required elements read from the design's own HTML: text, fonts, colours and sizes
  • Twelve fixed edits in Edit Mode and the undo button
  • Ten export checks: PNG, HTML, fonts, resolution, watermark, SVG, PDF, Figma, bulk and assets
  • Terms of use, privacy policy and pricing page read

Not tested or limited

  • Only two of the three fixed briefs were run. The landing brief used 4 of the 20 free credits for the day and the app brief used the other 16, which took the day's allowance to 100 per cent and past the 85 per cent stop. The cost of a brief is not shown before it is sent, so the stop could not be applied in advance
  • The bakery brief (an Instagram post, a story and a banner at set pixel sizes) was not run: the credits were gone, and the tool makes pages and app screens rather than fixed-size social pieces
  • The pricing page says up to 3 screens a day, yet the five-screen app brief was built in full; I report what happened
  • The 360 and 768 pixel views were checked on the landing page only, with the preview's tablet and phone buttons (768 and 390 pixels). The app screens are fixed 390 by 844 phone frames
  • The twelfth edit, regenerating one element from a written instruction, could not be run because the credits were at zero; the prompt box took the text and did nothing
  • Brand kit was not graded: ten new designs do not fit a day of 20 credits
  • Collaboration was not graded: every point needs a second account. The Share dialog offers Private or Anyone with the link, which lets people view
  • Copy to Figma finished, but I did not paste the result into Figma, so the Figma point of the export check is not counted. React export costs 2 credits and the all-screens ZIP is a paid feature, so neither was run
  • No plan was bought, so renewal prices and paid exports were not tried

Still to test

  • The bakery brief, brand kit and the written-instruction edit on a day with fresh credits
  • Collaboration with a second account
  • React export and the all-screens ZIP on a paid month
  • Pasting the Figma copy into Figma
What these results meanRead the full UXMagic review