Test log
Google Stitch test data
Raw results for the Google Stitch 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
- 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 | Median brief to draft: About 2 minutes | 5/5 |
| T04 | Brief Adherence | Required elements right: 45 of 60 | 2/5 |
| T05 | First Draft Quality | Design faults: 18 | 2/5 |
| T06 | Editing Freedom | Edits that worked: 6 of 12 | 2/5 |
| T07 | Export & Handoff | Points that worked: 5 of 10 | 2/5 |
| T08 | Rights & Commercial Use | Owner of the output: You | 3/5 |
| T09 | Pricing & Value | Cost of the whole run: $0 | 5/5 |
| Overall (in the review) | 3/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: Stitch's nearest feature is a design system with a DESIGN.md file, and it reads colours and a font. I used it for the colour and font edits only, and did not run ten generations.
- The ten generations would fit the 400 daily credits; they were left out to keep the run short.
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. A Share button exists.
- Needs a second test account.
Brief to First Draft
5/5Tested- Method
- Each fixed brief was typed into the home prompt box with the logo and photos attached.
- Median brief to draft
- About 2 minutes
- Credits used in total
- 23 of 400
- Remark
- Scale 5: median under 5 minutes.
Raw notes
Each fixed brief was typed into the home prompt box with the logo and photos attached. The clock ran from pressing send to the moment the Play button appeared in the top bar, which is when Stitch finishes.
The bakery set was finished about 65 seconds after I sent the brief, the landing page about 2 minutes (123 seconds) and the five-screen app about 3 minutes 36 seconds (216 seconds). The median is the landing page.
The project opened about 13 seconds after sending, with grey placeholder frames. The text appeared first, then the pictures loaded in, and the screens were still fading in for about a minute before the Play button came.
The app brief cost 11 credits and the landing page 3. Everything I did, including the bakery set and six edits, used 23 of 400 daily credits.
- Times are read from screenshots taken every six seconds, so each is accurate to about six seconds.
Brief Adherence
2/5Tested- Method
- Twenty required elements per brief were checked in the first drafts: sizes from the canvas labels, text, fonts and colours from the exported code, pictures by eye.
- Required elements right
- 45 of 60
- Invented claims
- Many
- Remark
- Scale 2: 30 to 44 of 60 right, or invented reviews or claims. The count sits in the band above, but the invented quote and offers set the grade.
Raw notes
Twenty required elements per brief were checked in the first drafts: sizes from the canvas labels, text, fonts and colours from the exported code, pictures by eye.
45 of 60 were right: 18 of 20 for the bakery set, 14 of 20 for the landing page and 13 of 20 for the app. Every line of text I supplied was used word for word, and the logo, loaf, pastry and yarn photos were used.
What failed was the look: Stitch set headlines in Newsreader, not Fraunces, and replaced my brand colours with its own palette on the app and the landing page, for example a pale blue background instead of cream #F7F3EC. The screens were not 390 by 844 (they were 884, 1428, 1031, 892 and 1214 tall), the landing page was 1280 wide, not 1440, and the bakery pieces are one board with half-size previews. The studio photo is not visible on the Welcome screen.
Stitch also invented content: a quote from a named dyer, "Only 3 spots remaining", "15% off", a street address in Portland, a booking number and a pre-filled customer name. Its chat said it had used Fraunces and 390 by 844 pixels.
- Colours are counted as right only when the exact hex value is in the page code.
First Draft Quality
2/5Tested- Method
- The exported code of each draft was opened at 360, 390, 768 and 1440 pixels wide.
- Design faults
- 18
- Remark
- Scale 2: 11 to 20 faults.
Raw notes
The exported code of each draft was opened at 360, 390, 768 and 1440 pixels wide. Contrast was worked out from the colours on screen, and each kind of fault was counted once per design.
18 faults: 4 on the landing page, 7 on the app and 7 on the bakery set.
The bakery set had seven pale small texts, including white on orange "Order now" at 2.45 to 1 where AA asks 4.5. The app had calendar letters at 4.05 and faded dates at about 2, a cut-off date line, a cut-off summary line, calendar cells under 44 pixels and a name already filled in. The landing page cut off three product descriptions and has links under 44 pixels.
Nothing overflowed sideways at any width, and the headline and body sizes were clear. In the exported preview pictures the logo appears as broken-image text on some screens.
- Stitch builds one layout that adapts, so the 360 and 768 views are the same code, not separate designs.
Editing Freedom
2/5Tested- Method
- Twelve fixed edits on the generated landing page.
- Edits that worked
- 6 of 12
- Remark
- Scale 2: 4 to 6.
Raw notes
Twelve fixed edits on the generated landing page. An edit counts when it did what was asked with a normal control and no workaround.
Six worked: one colour changed through the design system, the text edit worked in place (I typed a word into a heading), a new section was added from a written line in about 100 seconds, the canvas size changed by generating a mobile version (a new screen in under 100 seconds), a written instruction replaced one photo with a blue skein, and three undo steps reversed my last changes.
Six did not: the font change added Fraunces to the design system but the headlines in the code stayed in Newsreader; the photo upload was refused with "File not allowed" (a PNG and a JPG, and again on a retake the same day); dragging an element only selected another one; and I found no control to resize a text box, align with guides or lock an element. The element menu holds only Edit Text, Edit With AI and Delete.
The design system change took about 30 seconds. The font does exist in the list, so the miss is in the page code, not in the font menu.
- I retook the image upload later the same day, by hand through the file picker with a JPG and a PNG; the PNG was refused again with "File not allowed" (the JPG did not change the photo), although the same PNG is accepted in the home prompt box. The edits were done on the landing page only.
Export & Handoff
2/5Tested- Method
- Ten export points tried on the finished designs: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma, 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
- 5 of 10
- Remark
- Scale 2: 3 to 5.
Raw notes
Ten export points tried on the finished designs: PNG at the brief size, SVG, print PDF with bleed, an editable file for Figma, code that runs on a plain host, fonts named, full resolution, bulk export, no watermark and export of the source assets I uploaded.
Five of ten worked: a zip with the code of every screen, the code opens as a plain page, the fonts are named in a Google Fonts link, the whole set exports in one zip, nothing carries a watermark, and the logo and photos I uploaded are in the zip.
Five did not: there is no PNG export at the brief size (the zip holds a preview picture capped at 1600 pixels tall, 723 by 1600 for the 1280 by 2833 landing page), no SVG, no print PDF and no full-size picture. The Figma option sends the page to a converter called code.to.design, so I did not run it.
- The Figma export was not tried because it passes the page to a third party.
Rights & Commercial Use
3/5Tested- Method
- I read Google's terms of service from the Terms & Privacy link in the account menu, and the Stitch settings page, and looked for a training opt-out.
- Owner of the output
- You
- Training on my files
- Off, can be changed
- Remark
- Scale 3: commercial use is not stated.
Raw notes
I read Google's terms of service from the Terms & Privacy link in the account menu, and the Stitch settings page, and looked for a training opt-out.
Ownership is clear in Google's general terms: "Some of our services allow you to generate original content. Google won't claim ownership over that content." Those terms and the Stitch terms I saw say nothing about commercial use of designs.
Training is controlled by a setting: "Allow AI model training", which was unchecked on my account. I found no promise of protection against claims over generated content.
- I read the pages above, not the whole Stitch additional terms, and I am not a lawyer.
Pricing & Value
5/5Tested- Method
- I looked for plans on the account and in the product.
- Cost of the whole run
- $0
- Daily credits
- 400
- Remark
- Scale 5: under $120 a year, the briefs fit the allowance. No renewal price exists to compare.
Raw notes
I looked for plans on the account and in the product. The only allowance shown is on the settings page.
Stitch showed no price and no paid plan. The settings page shows 400 daily credits, and the whole run of three briefs, twelve edits and exports used 23 of them. The product is marked BETA.
Because there is no plan to buy, I could not check a renewal price. Everything I tested worked without paying.
- The product is in beta, so its allowance and price may change.
Other features checked
Coverage
Tested
- All three fixed briefs typed into the home prompt box with the logo and photos attached
- Twenty required elements per brief read from the exported code and the canvas
- A design fault check of the exported code at 360, 390, 768 and 1440 pixels
- Twelve fixed edits on the landing page
- Export zip, code view, the export panel and the Figma option
- Google's terms of service and the settings page read
Not tested or limited
- Brand kit was not graded: it needs ten new generations, and the nearest feature, the design system, was only used for the font and colour edits
- Collaboration was not graded: every point needs a second account
- The Figma export sends the page to a third-party converter, so I did not run it
- The Stitch additional terms were shown once at sign-in; I read only the first lines and Google's general terms
- Stitch has no pricing page and no paid plan on my account, so there is no price to track and no renewal price to check
- The twelve edits were done on the landing page only
Still to test
- Brand kit with ten generations
- Collaboration with a second account
- The Figma export through its converter
- Bakery set edits