Test log
Flowstep test data
Raw results for the Flowstep review. The verdict is in the review.
- Tested
- 8 November 2026
- Tester
- Miles Foster
- Account
- Free demo account, signed up by RankDude, nothing paid to the brand
- Tests
- 9
- Screenshots
- 7
- Method
- Published methodology
- Environment
- Google Chrome on desktop
Results
| ID | Test | Key measurement | Score |
|---|---|---|---|
| T01 | Brand Kit & Consistency | – | n/a |
| T02 | Sharing & Collaboration | – | n/a |
| T03 | Brief to First Draft | Bakery set, three pieces: Under 45 seconds | 5/5 |
| T04 | Brief Adherence | Required elements right: 43 of 60 | 2/5 |
| T05 | First Draft Quality | Design faults: 17 | 2/5 |
| T06 | Editing Freedom | Edits that worked: 9 of 12 | 3/5 |
| T07 | Export & Handoff | Points that worked: 6 of 10 | 3/5 |
| T08 | Rights & Commercial Use | Output ownership stated: Yes | 4/5 |
| T09 | Pricing & Value | Starter, paid yearly, a year: $144 | 4/5 |
| Overall (in the review) | 3.9/5 | ||
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 new designs would take the trial's 15 messages past my 85 per cent stop. Flowstep has themes and file instructions for colours, rounding and written rules, and a theme was used in the editing test.
- Needs a paid month.
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. Flowstep's docs say a shared link is view-only, anyone can open it without an account, and giving someone edit access needs a paid seat.
- Needs a second test account.
Brief to First Draft
5/5Tested- Method
- Each brief was typed into a fresh file with its logo and photos attached.
- Bakery set, three pieces
- Under 45 seconds
- Booking app, five screens
- 50 seconds
- Landing page
- 34 seconds
- Messages for the three briefs
- 3 of 15
- Remark
- Scale 5: median under 5 minutes.
Raw notes
Each brief was typed into a fresh file with its logo and photos attached. The clock ran from pressing send to the Created card appearing in the chat; a screenshot was saved every few seconds and the whole run was recorded.
The bakery set (three pieces) was finished in under 45 seconds, and the first screens were on the canvas about 25 seconds in. The five-screen booking app took 50 seconds. The landing page took 34 seconds.
The median is about 40 seconds. Each brief was one message, so the three briefs cost 3 of the trial's 15 messages.
- Times come from screenshots saved every few seconds and the screen recording, so they are good to about 5 seconds.
Brief Adherence
2/5Tested- Method
- The 20 required elements of each brief were read from the designs' own HTML (text, font, colour and size of every element) before any edit.
- Required elements right
- 43 of 60
- Bakery, app, landing
- 15, 14 and 14 of 20
- Lines of text added
- 34
- Remark
- Scale 2: 30 to 44 right. The text and the supplied files were handled well, but brand colours, fonts and sizes were not kept.
Raw notes
The 20 required elements of each brief were read from the designs' own HTML (text, font, colour and size of every element) before any edit. Colours are compared as hex values, with a tolerance of 3 on each channel.
43 of 60 were right: 15 of 20 for the bakery set, 14 for the app and 14 for the landing page. Every headline, line, price, address and set of hours matched word for word, the five buttons and links were right, and the supplied logos and photos are in place on every piece.
The misses are the same in all three briefs. The brand colours were rebuilt as the tool's own theme: the landing page's oat background reads #F5ECD7 instead of #F4EEE3, its button #4F6A31 instead of #5B7B52 and its text #261A12 instead of #3B2F2A, and berry and gold appear nowhere. No headline is set in Fraunces. Three sizes are off: the banner is 820 by 400 pixels instead of 312 tall, the app screens are 402 by 874 instead of 390 by 844, and the landing page is 1140 pixels wide instead of 1440.
The tool also added 34 lines of text I did not supply, such as a small label above each headline, a line under each product, a Save your seat link and a footer tagline. No prices, reviews or stock photos were invented.
- Colour is read from the rendered design, so a tolerance of 3 on each channel is allowed. A name and price shown on separate lines count as the card text.
First Draft Quality
2/5Tested- Method
- Every piece was opened at its own size, the app screens and the landing page also at 360, 768 and 1440 pixels.
- Design faults
- 17
- Text failing contrast
- 6
- Remark
- Scale 2: 11 to 20 faults. A component that repeats, such as the back button, is counted once.
Raw notes
Every piece was opened at its own size, the app screens and the landing page also at 360, 768 and 1440 pixels. Contrast was calculated from the real colours, or from the pixels behind text on a photo. Tap targets were measured.
17 faults. Text contrast failed in six places: four lines on the bakery photos (between 2.9 and 3.8 to 1) and two on the landing page (3.7 and 4.35 to 1). On the app, the back button is 40 pixels, the month arrows 32, the Get started and Continue buttons 36, and the last button of the booking has only an icon and no label. The three form fields are filled with example details.
On the landing page the product pictures are plain coloured circles. At 360 pixels the page runs 459 pixels wide so it scrolls sideways, the headline is cut off and the three product cards are squeezed into thin columns. At 768 and 1440 pixels it held together, and the five app screens had no sideways scroll at any width.
- The 360 and 768 views were made from each screen's own HTML, because the preview has no device switch.
Editing Freedom
3/5Tested- Method
- Twelve fixed edits on the landing page, done with the controls a person uses.
- Edits that worked
- 9 of 12
- Messages for edits
- 3
- Remark
- Scale 3: 7 to 9.
Raw notes
Twelve fixed edits on the landing page, done with the controls a person uses. An edit counts when it did what was asked with no workaround. The design's HTML was read before and after each one.
Nine worked. A font was changed across the whole design with one chat message, a theme colour was changed everywhere with one Publish, an element was moved by dragging, a text box was resized from 498 to 380 pixels, one word was changed in place, a section was duplicated, the page was set to 1440 pixels wide with the layout kept, one button was recoloured from a written instruction in about 20 seconds, and three undo steps put everything back.
Three did not. Selecting two or more elements switches the panel off, so three elements cannot be aligned with each other. A new picture can be swapped in, but there is no control to choose how it is cropped. I found no lock control.
Edits made by hand cost no messages. The font change and the button change cost one message each, and the font took a second message because the first, Fraunces, is written into the code but never loaded.
- The font edit and the button edit are the two that need a message. Fraunces was not shown on screen even after it was asked for.
Export & Handoff
3/5Tested- Method
- Ten export points tried on the real files: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma, code that builds on a plain host, fonts named, full resolution, bulk export, no watermark and export of the source assets I uploaded.
- Points that worked
- 6 of 10
- Post PNG size
- 2160 by 2160
- Remark
- Scale 3: 6 or 7.
Raw notes
Ten export points tried on the real files: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma, code that builds on a plain host, fonts named, full resolution, bulk export, no watermark and export of the source assets I uploaded.
Six of ten worked. The export dialog saves each piece as its own PNG, with no watermark: the post is 2160 by 2160 pixels and sharp. The code ZIP is a Vite project with React and Tailwind; it built into a static site after the one setup step its README names, which fetches three small components. The ZIP holds my uploaded logo and photo, and the page names its fonts.
Four did not. The PNG is always twice the design size, so it never matches the brief's size, and the banner comes out at 1640 by 800. There is no SVG and no PDF. Copy to Figma put a Figma clip on the clipboard, but I did not paste it into Figma, so I did not count it.
The trial unlocks all of this. Flowstep's docs say that after the trial, exporting to Figma, code or image files needs a paid plan.
- The Figma point needs a paste into Figma, which was not done. Free-plan export after the trial was not observed.
Rights & Commercial Use
4/5Tested- Method
- I read the Terms of Use (last updated 17 December 2025) from the link in the site footer, and the data privacy page in the docs, and looked for ownership, commercial use, model training and an indemnity.
- Output ownership stated
- Yes
- Training on your files
- Not used
- Indemnity
- None found
- Remark
- Scale 4: ownership and use are clear, no indemnity.
Raw notes
I read the Terms of Use (last updated 17 December 2025) from the link in the site footer, and the data privacy page in the docs, and looked for ownership, commercial use, model training and an indemnity.
The terms say "Users retain ownership of their User Content", and User Content includes the designs, prompts and files you make or upload. Flowstep gets a licence to host and process them only to run the service. The docs add that Flowstep does not use your personal data to train its models and that its model providers may not either, apart from anonymous feedback.
The terms put no limit on how you use your designs and do not tie commercial use to a plan, but they do not say so in words either. I found no indemnity for generated content.
- No lawyer's reading; only the pages above. A contract that is silent on commercial use is not a promise either way.
Pricing & Value
4/5Tested- Method
- Plans were read on the public pricing page in both billing views and every message tier was selected; the plan panel in the product gave the allowance.
- Starter, paid yearly, a year
- $144
- Starter, paid monthly
- $15 a month
- Remark
- Scale 4: $120 to $199 a year.
Raw notes
Plans were read on the public pricing page in both billing views and every message tier was selected; the plan panel in the product gave the allowance. Nothing was bought.
The cheapest paid plan, Starter, is $12 a month paid yearly, about $144 a year, or $15 a month paid monthly. It gives 80 messages a month, unlimited exports, Copy to Figma and unlimited projects. Pro (240 messages) is $23 a month paid yearly and Max (1000 messages) $80. Prices are per seat.
Free after the trial gives 3 messages a day and 20 a month. The three briefs I ran took 3 messages, which is a whole day of the Free plan, and each paid plan covers them many times over.
- No plan was bought; renewal prices were not seen. The terms do not say what the Free plan locks beyond exports.
Other features checked
Coverage
Tested
- The three fixed briefs, each with its logo and photos attached
- Sixty required elements read from the designs' own HTML: text, fonts, colours and sizes
- Twelve fixed edits and the undo shortcut
- Ten export checks: PNG, SVG, PDF, Figma, code that builds, fonts, resolution, bulk, watermark and source assets
- Terms of use, the data privacy page and the pricing page read
Not tested or limited
- The account was on the 3-day trial, which unlocks exports and 15 messages. The Free plan that follows (3 messages a day, 20 a month, limited export) could not be observed, because the trial runs to 11 November. What the Free plan locks comes from Flowstep's own pricing page and the plan panel
- Brand kit was not graded: ten new designs would take the trial past its 15 messages, and I stop at 85 per cent of any allowance. Six messages were used in all
- Collaboration was not graded: every point needs a second account. Flowstep's docs say a shared link is view-only and that giving edit access needs a paid seat
- Copy to Figma put a Figma clip of 153 KB on the clipboard, but I did not paste it into Figma, so the Figma export point is not counted
- The 360 and 768 pixel checks were done on the landing page and the five app screens by opening each screen's own HTML at those widths; Flowstep's preview has no device switch
- The brief's Fraunces font was asked for again after the first draft and written into the code, but Flowstep does not load it, so the page showed the fallback font; Playfair Display worked
- No plan was bought, so renewal prices, the Pro and Max plans and the paid exports after the trial were not tried
Still to test
- Brand kit with ten designs on a paid month
- Collaboration with a second account
- The Free plan's exports once the trial ends
- Pasting the Figma copy into Figma