Learn how to turn a prompt into prototypes, websites, posters, and more with Genspark Design. Refine everything on the Canvas, then ship runnable code with Build it.
Updated Nov 16, 2026
Overview
Key Features
Troubleshooting
FAQ
Genspark Design
What is Genspark Design?
Genspark Design (Design / Prototype in the agents list) is a canvas where you describe a design in plain language and the agent builds it: a landing page, an event poster, a deck, a clickable prototype, a brand system. You write the request, answer a question or two if the brief is thin, and the design appears on the canvas beside the conversation. Then you refine it on the canvas, in chat, or both.
Design doesn't retouch uploaded photos, apart from editing an image layer on a poster, and it doesn't make video ads. Those happen in Media Studio. Photo editing has the line between the two products.
The screen splits in two. The chat panel on the left is where you ask for things. The canvas on the right is where the design lives, and where you click into text, adjust sliders, pin comments or draw on it. You don't need design software experience to use either one.
You can bring your own material from the start. The + button attaches a Figma file, a screenshot, files from your AI Drive, a code folder or Connect GitHub, a web element you capture from a page, or a Design System you or your team already made. A reference gives the first generation something to match.
Who it's for: founders, marketers, product managers, designers and small teams who want a design made from a description.
What you can do
Six jobs cover most of what people bring to Design. Each one has a full recipe at the end, with the steps and a prompt you can copy.
| What you can do | Full recipe |
|---|---|
| Build a website or landing page from one brief, then hand it to Genspark Code and publish it | Recipe 2 |
| Make a poster or flyer for an event, then take it out as a PNG, a PDF or a layered PSD | Recipe 3 |
| Turn an outline into a slide deck, then export PPTX for editing or PDF for sending | Recipe 4 |
| Build a clickable prototype, present it in a new tab, and share a link a reviewer can click through | Recipe 5 |
| Produce a social set in several sizes from one brief | Recipe 6 |
| Make a logo and a brand kit, save them as a Design System, and reuse them on every later project | Recipe 7 |
The recipes section also covers the jobs that come up less often: a business card or another print asset, packaging on a dieline (the flat outline of a pack), a logo animation, a review round, a flipbook, a wireframe, and a page built around a photo you already have. Recipes lists all of them.
Quick start
One design, from an empty box to something you can show someone. All you need is a browser and a Genspark account.
- Open Design / Prototype from the agents list and sign in. The home page has the input box in the middle, Popular Tasks examples under it, and your earlier work in My Designs.
- Describe the design. Say what it is, who it's for and what it should achieve in one or two sentences. A size, a mood and a color help: "a one-page site for a coffee subscription, warm and quiet, cream and dark green."
- Attach what you have with the + button in the input box: a screenshot, a Figma file, a document or a code folder. A saved brand goes in with the Design System selector beside it, and Context you can attach lists the rest.
- Send it. The agent may ask a couple of questions first, about format, size or style. Answer the ones that matter and let the rest go, or it may start straight away.
- Watch it build. The conversation fills with the plan and the steps, and the canvas fills with the design. A first pass is a starting direction.
- Make one change. Click the text you want to change with Edit, or drag a Tweaks slider for color and spacing. Both write straight into the design without a new generation.
- Take it out. Present opens it in a new tab for presenting, Build it hands the design to a Genspark Code project, and the Share menu and the Download button cover links and files. Exporting has the format table.
A one-page site for [a coffee subscription] called [name]. Warm and quiet: cream background, dark green type, one large photograph of a pour-over. Sections: the offer, how it works in three steps, two customer quotes, a closing sign-up. Desktop first, then show me the phone version.

Tip: Popular Tasks under the input box fills a ready-made prompt you can edit before sending. It's the fastest way to see what a good brief looks like.
Note: Standard and Ultra are billed differently. Ultra is the default, so the first run uses credits unless you check the selector and switch before you send. Standard and Ultra has the plan details.
Two habits make the first design go better. Put the type, the size and the audience in one message, because a short brief means a round of questions, and a question is a billed turn like any other. And when the first pass comes back wrong, say what's wrong with the part that's wrong, and leave the rest of the prompt alone.
Context you can attach
The + button is where a design gets its references, its brand and its content. Eight kinds of input sit behind it, and two of them sit in its Code group.
| What you attach | What it does |
|---|---|
| Local files, images and docs | Uploads the file into the project. Screenshots of layouts you like work well here |
| Files from AI Drive | Pulls a file you already keep in AI Drive into the project |
| A Figma file | Uses the frame's layout, spacing and type as a reference for the generation |
| Attach code folder | Adds a filtered, capped snapshot of small local text/code files to the next message |
| Connect GitHub | Connects your account so the agent can work with repositories you authorize |
| A past design | Reuses one of your earlier projects as the visual reference |
| A web element | Captures one element from a page you point at, with its styling |
| A Skill or a Design System | Applies a saved working method or a saved brand |
Attach code folder caps its snapshot at 80 files, 256 KB per file and 2 MB in total, text and code only, and the agent doesn't run what it reads. Connect GitHub keeps a live connection to the repositories you authorize.
Attaching isn't the same as importing. A code folder or a Figma file used as a reference guides the look. A file imported with + becomes content in the project, and you can place it on the canvas.
What to attach follows from what the first pass got wrong. Layout right and look wrong: a screenshot you like. Look right and spacing wrong: a Figma frame. Brand wrong on every page: a Design System, which decides palette and type first. Copy wrong: attach the document. Note that + reads a document when you send the message, so it won't follow later edits to the source.
For coding work in a full developer environment, Genspark Code is the product to use. Design builds the interface and the page, and stops at the file you download or the Code project you hand it to.
Where everything is
Three areas carry the work: the chat panel, the canvas and its toolbars, and your project list.
The canvas toolbar
The top right of the canvas holds the four controls that change the design itself: Tweaks, Edit, Comment and Draw. The table under The editing tools says what each one does and when to reach for it. Someone who has the design read-only doesn't see any of the four, so a read-only reviewer can look and remix, and nothing else.
The delivery controls sit in the top bar instead, because they take the design somewhere else.
The chat panel on the left holds your prompts, the agent's plan and its list of steps, any question it needs answered, and the preview of a page before a download. A long build fills it with steps, so the last message usually says whether the run finished.
Canvas tabs and the top bar
The tab strip above the canvas carries the Design System tab, which appears only in a Design System project and is where a brand is built and reviewed. In any other project, the Design System selector beside the prompt input opens a browse grid of saved systems.
The top bar is the delivery row.
| Button | What it does |
|---|---|
| Present | Opens a new tab for presenting. Arrow keys move between pages, and a deck carries its Speaker Notes |
| Build it | Sends the design to a new Genspark Code project. It offers Website and App, and opens the project in a new tab when the handoff is ready |
| Download | Downloads the project's source as a ZIP. For an owner or an editor it may take an agent turn first, which can use credits; a read-only viewer gets the file straight away. It's disabled while a generation is running |
| Share menu | The share link, Bookmark, Add to Hub (see Sharing and collaboration), and Create design system from this project |
Present is the cheapest check you have: the design at full size, without a download. A page that looks fine at canvas zoom can read badly on a screen.
Download takes the whole project, not one page: the source files, for a developer or an archive. A single PNG or a PSD comes from the Export menu when the page is built as a poster. See Exporting for the difference.
The editing tools
| Tool | How you use it | Best for |
|---|---|---|
| Tweaks | Drag sliders and pick colors in a live panel | Global changes: palette, spacing, type scale |
| Edit | Click one element, then change it in the panel | Text and style on a single element |
| Comment | Pin a note on the canvas, collect several, then send them together | Describing a change in words |
| Draw | Draw on the canvas with the red brush, or drop sticky notes, then send | Pointing: an arrow, a circled area, a rough shape |

Tweaks is empty on a first design until the agent generates controls for it. Ask for "make this tweakable" in the chat and the panel fills in.
The choice between them comes down to what the change is. A value that already has a control (a color, a spacing step, a type size) belongs in Tweaks, because a slider sets the value exactly and costs nothing. A word or a price belongs in Edit, for the same reason. A change that isn't a value at all, like a section that should be somewhere else, belongs in the chat, because it has to be rebuilt, not set.
Comment and Draw exist to stop you describing a position in words: "the block under the second heading" is ambiguous on a page with two similar blocks. Collect several notes and send them together. One message with five pins is one turn. A pin is saved in your browser, and nothing sends until you click Send all ({count}), which is one AI request. Another person's pins stay with them.
The Share dialog
| Setting | Options |
|---|---|
| Access | Anyone with the link, or Restricted with an email invite |
| Role | Viewer, Editor (Manager where offered) |
| Revoke | Set General access to Restricted. People already invited, or with Hub access, may still open it |
A public link opens the design and its source files to anyone who has the URL, with no sign-in. Downloading a file from it still follows what that viewer's own account can download. See Sharing and collaboration.
Where your designs are saved
Your designs are saved in the My Designs gallery on the Design home page. It holds every project you've made, and clicking one reopens it with its conversation, its versions and its files.
| What you want to do | Where it is |
|---|---|
| Find an earlier design | My Designs on the Design home page |
| Keep a copy before a big change | Duplicate in the project's menu |
| Start from someone else's design | Remix on the shared design |
| Rename or delete | The project's menu in My Designs. Deleting asks once and can't be undone |
An organization can lock project deletion for its members. When that's on, a delete is refused, and that covers the project behind a Design System as well. Ask your org admin whether the lock is on.
The gallery is the only list, so the project's name is what you'll search with later: name it after the thing it's for, not the agent's working title. A design someone sent you and you remixed lives in your own gallery. The original stays with whoever owns it.
Design types
You don't pick a type. Describe the thing and the agent routes to one of these. Saying the type in the prompt still helps, because it sets the page size, the export options and whether a Present mode makes sense.
| Type | Best for | What you get |
|---|---|---|
| Prototype | Apps, dashboards, sign-up flows, anything with screens | Linked screens that present in a new tab, and a share link a reviewer can click through |
| Slide deck | Pitch decks, reports, training material | Pages that Present flips with the arrow keys, plus PPTX and PDF exports |
| Poster | Events, promotions, print pieces | A single page with the poster export menu: PNG and layered PSD |
| Video / Frame Movie | A logo animation or a short product intro | A frame-movie clip, exported as MP4 from Export video |
| Wireframe | Laying out a screen before committing to a look | A low-fidelity page to argue about structure, then a full design built from it |
| Flipbook / Paged Book | Lookbooks, catalogs, whitepapers | A multi-page document that reads as pages, and exports as a PDF through the print dialog |
The type decides the page size, which formats appear in the export menus, and whether there's anything to present. A poster with the wrong type comes back at page dimensions where you wanted a sheet, and a deck with the wrong type comes back as one long page. When the output is structurally wrong (the wrong page size, the wrong shape), check the type first. The fix is a rebuild in the type you want, not a restyle.
Prototype is for anything with more than one screen. The value is the links between screens, so ask for them explicitly: which screen leads to which, and how a reviewer gets back.
Slide deck is pages you flip. Say the slide count and one idea per slide. Eighteen slides when you wanted eight is a brief problem.
Poster is the single-sheet type. When the canvas detects a poster layout with layers, the Export menu offers Export image for a PNG and Export PSD for a layered file. If you need an image file and not a page, build the design as a poster.
Video / Frame Movie is the only video shape Design builds: a short piece assembled frame by frame on the canvas and exported as MP4, which suits a mark that draws on or a product that turns once. Live footage, cuts and ads belong to Media Studio.
Wireframe is a low-fidelity page whose job is to settle structure. It looks unfinished on purpose: arguing about where a section goes is cheaper before the styling exists.
Flipbook / Paged Book reads as pages, not one long canvas, which is what a catalog or a lookbook wants.
Design builds designs, and it doesn't retouch uploaded photos, apart from editing an image layer on a poster. Video ads and photo retouching happen in Media Studio. A frame movie is the one video shape Design builds, and it's the one for a logo animation or a short product intro.
Design or another tool
Four Genspark products make visual work, and the choice is usually obvious once you know what each one is built for.
| Product | What it's for |
|---|---|
| Genspark Design | Pages, posters, decks, prototypes, brand systems and frame-movie shorts. One canvas that produces a design in several formats |
| Media Studio | Video, audio and 3D, plus image work that goes past one picture: layers, retouching, video ads |
| AI Image | One picture, generated or edited |
| AI Slides | Presentations, with a slide editor of its own and PPTX and Google Slides export |
Media Studio also makes posters, from key art. For a poster that's part of a brand with a site, a deck and a logo, use Design.
The two that overlap are Design and AI Slides. For a deck you'll keep editing in PowerPoint or Google Slides, start in AI Slides. For a deck that has to match a website, a poster and a logo, build it in Design.
Credits and costs
The bill follows the work the agent does, which is why a long session can cost more than a short one that produced more, and why a one-line request can cost more than a whole page.
Standard and Ultra
Every project runs on one of two tiers, chosen in the selector beside the input box. Standard is the faster, cheaper tier, and it's the only one that can draw on Free Quota. Ultra is the stronger tier for long briefs and heavy revision, and it bills credits.
Ultra is the default. Check the selector before you send: switch to Standard before a long working session if you're on a plan with Free Quota and want the session to come out of it.
Standard turns draw on your plan's Free Quota on Plus, Pro and Go. Ultra and named image models use credits. Free accounts use credits only. A Team or Enterprise seat doesn't currently include Free Quota. If you also have a personal Plus, Pro or Go plan, its Free Quota applies.
The selector panel shows Weekly free quota and how much of it is left, along with when it resets. Once the allowance is used, the same session continues on credits.
If Ask First is enabled, you'll be prompted before switching from exhausted Free Quota to credits. The card offers to wait for the reset, continue with credits, or not ask again.
The tier changes more than the price. Ultra holds a long brief together better and is where a heavy revision round belongs. Standard is the right place to explore directions and fix copy. A practical pattern: Standard while the design is still changing shape, Ultra for the pass that has to land, then back for corrections.
On a Standard turn, the image work has a narrower allowance than the text work. Design's default image model at default quality can come out of the same Free Quota as the rest of the turn. Named image models, higher quality, 4K, video, audio and image edits use credits on any tier.
What bills credits
The table answers six common questions about a charge.
| What happened | Why it billed |
|---|---|
| I asked a question in the chat and nothing was built | The turn is the work. Planning, research and revision in the chat are a billed turn like any other |
| I sent the same request twice | The second send is a new generation, not a retry of the first |
| I asked for ten directions | Ten attempts ran, and each one is charged |
| A short prompt cost more than a long one | The bill follows the work the agent did, not the length of what you typed |
| I added images | Images beyond the default model at default quality, plus video, audio and image edits, bill on top of the turn |
| An image or video was blocked as NSFW | The image or video isn't charged, and the rest of the turn is |
A turn that only talks still costs, because the answer is the work. A short conversation feels lighter than a build, but the agent reads the project, decides what to change and produces the next step either way.
Additional generations may use credits, and the cost depends on the work performed, so make each request count: name the element, say what stays, and send one change at a time.
A model or cost confirmation may appear depending on your account and settings. An image count in your prompt is guidance, not an enforced limit.
Where to see it: open Credits in the account menu, then find the Design rows in Credit Usage History. The Credits Guide explains how a credit is counted, and Membership Plans has what each plan includes.
One thing to check before you blame the bill: the tier. A session that ran on Ultra wasn't drawing on Free Quota, however long the design sat on Standard before it. If a project's costs jump and nothing else changed, look at the selector first.
Habits that keep spend down
- Ask for a sample first. "Show me three directions for the hero" costs less than "build ten pages", and you keep the one you like.
- Change one thing at a time. Small separate edits are cheaper than one rework, and they're easier to keep.
- Use the direct paths. Tweaks and a click into Edit for text and color cost nothing extra. A chat request for the same change is a generation.
- Look before you order again. The preview shows a new or restyled page before the download is offered, and that's the moment to stop a direction that isn't working.
- Duplicate before the big one. A copy you can fall back on saves a rebuild, and duplicating is free.
- Write the brief once, well. Type, size, audience and style in the first message removes the question round, and the question round is billed.
Refunds
If a run fails because of a system error, or ends without producing anything, its credits are returned automatically, up to a daily limit. Not every incomplete or disappointing result qualifies: a run that produced work, or that you stopped, is charged. A retry is a new run and uses credits. A request blocked before it starts runs nothing and costs nothing.
A refusal that delivers nothing isn't charged either, even when the agent read your files or searched before it stopped.
The distinction is the one above. If a failure looks like it should have been refunded and wasn't, report it with the project link. How do I report a problem? has the steps.
Editing and edit safety
Two paths change a design, and they behave differently. One is exact and free, the other rebuilds and bills. When the change is a word, a color or a spacing value, use the first.
The direct path writes into the design without a new generation and without a credit charge. It covers a click into a text element with Edit, and the sliders in Tweaks: color, spacing, type scale, alignment. It's exact, because you're setting the value.
The redraw path sends the change to the agent as a prompt. Layout changes, structural changes, new elements, a new section, a restyled page all go this way. A redraw bills, and it rebuilds more than the part you named, so other parts of the page can move.
| What you want to change | Path | What to expect |
|---|---|---|
| A word, a headline, a price | Edit, click the text | Immediate, free |
| A color, a spacing value, a type size | Tweaks slider, or Edit on the element | Immediate, free |
| An image swap | Edit on the image | Usually direct. A redraw if the new image changes the layout |
| The order of sections, a new section | Chat, described precisely | A redraw, billed, with other sections possibly shifting |
| A whole page restyled | Chat, with the new direction | A redraw of that page, and the preview before a download |
Edit pins the element, not the specification. Naming the element you selected keeps that element in place. It doesn't keep the instruction you gave. Ask for "no black background" and a redraw can still come back with one, because the agent is rebuilding rather than applying a filter. The narrower the instruction, the more of the rest survives.
Reading a redraw is its own skill. Compare the result against the duplicate you made before it, separate what you asked for from what moved on its own, and send the correction against the part that moved. A second full request resets the work the first one did.
Four habits protect the rest of the design:
- Duplicate the project before a change you're unsure about. The original stays as it was.
- Change one thing at a time. Two changes in one message make it impossible to tell which one moved the layout.
- Point with Comment or Draw. A pinned note on the exact block, or an arrow drawn on the canvas, lands better than a sentence about "the middle bit".
- Check the result before the next request. A bad redraw that gets built on costs more than one that gets reverted by hand.
There's no element locking and no one-click undo. Duplicate before a major change, then compare the original and copy. Asking the AI to revert is a new request and may not reproduce the previous design exactly, so the copy is also your way back when a redraw goes wrong: make one narrow request about the part that moved.
Note: the Verifier is an extra check the agent can run in the background, and it uses credits. It only messages you when it finds something to fix, and you can stop it with Stop verifier. The pill just fades when you do, so a quiet run isn't proof the design passed.
Design System
A Design System is a saved brand: colors, fonts and components, applied to every design in a project. It's what makes the fourth poster look like the first three.
Create one from scratch with Design System below the input box, then Create New and enter a brand description. Import the raw material with a Figma .fig file, a GitHub repo or codebase, or uploaded files. The agent extracts the palette, the type and the components, and asks you to review and confirm before it saves.
Create one from work you already like with the Share menu → Create design system from this project. That's the fast path when a design already got the look right.
Use the Design System selector beside the prompt input to select a saved system for your project, or attach it with +. Every generation in that project then starts on-brand.
Review the extraction before you confirm it. What the agent extracts is a proposal: colors it read from your files, a type pairing, a handful of components. If one of those colors is a shade that came from a screenshot and not the brand, confirming it writes the wrong value into the system, and every design built from it inherits the mistake. Read the palette against the real brand values before you confirm.
A system earns its cost on the second project. The first pays for creating it; every project after that starts with the palette and type decided, which removes the most common revision loop: three redraws spent correcting a color the agent picked.
Exporting
Design leaves the canvas in six formats, as a Code project, or as a link. Which one you want depends on where the design goes next.
| Output | Where it is | What you get |
|---|---|---|
| Present | Top bar | Opens a new tab for presenting. Arrow keys flip pages, and a deck shows its Speaker Notes |
| Share link | Share menu | A URL anyone can open, or a restricted one with an email invite |
| Build it | Top bar | A handoff README written by the agent, then a new Genspark Code project opened in a new tab |
| ZIP | Download next to Build it | The project's source files, for a developer or an archive. For an owner or an editor it may take an agent turn first, which can use credits |
| PNG | Export menu → Export image | A raster image of a poster. The menu appears when the page is built as a poster |
| PSD | Export menu → Export PSD | A layered Photoshop file, one layer per design layer. Effects that can't rasterize are skipped, and the file still downloads |
| MP4 | Export video | A frame-movie clip |
| PPTX | Ask for "export as PPTX" in chat | Editable text and shapes, or screenshot-based slides for closer fidelity |
| Ask for "export as PDF" in chat | A print page, opened in a browser tab and sent to your print dialog |
Export video sits in the canvas top row and appears only when a frame-movie clip is open (not for a Viewer). It opens an Export composition dialog with Resolution, Frame rate and Start export.
Look before you download. A new or restyled page opens in the preview first, and that's the last cheap moment to catch a page that came back wrong.
Build it hands the design to a Code project, the share link hands it to a person, and Present hands it to a room. The rest are files, and the file follows from who opens it next: a PNG for a screen, a PSD for a designer, a PPTX for an editor, a PDF for a printer or a reader, an MP4 for a feed, a ZIP for a developer.
The poster exports are the narrowest. Export image and Export PSD appear only when the page is built as a poster, which means the canvas has detected a poster layout with layers.
Export fidelity
The PDF is printed by your browser. Design writes a print page and opens it in a new tab, and your browser's print dialog does the rest. Pop-ups are often blocked: allow them for the page, or use the link the agent posts in the chat.
Because the browser does the printing, the PDF is only as exact as a printed web page: fonts the browser can't find fall back, background fills depend on a setting that's off by default in most browsers, and the page size is what you choose in the dialog, not a size the design carries. That's fine for a proof and for reading on screen. It isn't a file a print shop can put on press, and Print size and paper says what to ask them instead.
Ask for editable PPTX when you need to change text and shapes; complex styling may change during conversion. For closer visual fidelity, ask for screenshot-based slides, whose individual elements aren't editable. If the exact look matters more than either, send a PDF.
Decide that trade before you export. A PPTX people can edit is right for a deck that keeps changing, even if a gradient flattens. A PDF that looks exact is right for a deck that goes out once. Sending both is common: the PPTX to whoever will edit it, the PDF to the room.
There's no vector export. No SVG, no Adobe Illustrator file, no EPS. The PSD is layered raster, which is why it opens in Photoshop but doesn't scale like artwork. Canva isn't an export either.
The raster limit catches people out on print: a poster PNG is rendered at three times the canvas size, and enlarging it past that still softens it. Check the downloaded image's resolution before enlarging it for print. The options are a bigger file or a printer who works from high resolution.
When a download is limited
Some accounts on the Free plan may be asked to upgrade to Plus to download ZIP, MP4, PPTX, PDF/print or poster PNG/PSD. Present, Share and Duplicate don't use credits. Build it is open on every plan, but preparing the handoff is an agent turn and uses credits.
The prompt is a dialog titled Export Design, with a Download with Plus button, and options to share the design with a teammate to view online or to hold off. It's an account-level test and not a plan rule, so two people on the same plan can see different things, and it can lift without a plan change. A Plus, Pro, Team, Enterprise or Go account isn't asked to upgrade.
If a download prompt appears, the design is still presentable, shareable and duplicable, and Build it still works.
Print size and paper
Print options depend on the design type. Flipbooks can carry exact paper sizes, bleed and crop marks: ask the agent to configure them, then verify the PDF dimensions and your printer's requirements. A poster or a business card has no bleed and no crop marks.
For a flyer on office paper, or a proof, the browser's dialog is enough. For a print run, ask your printer what they need, then set the paper size and turn on background graphics before you print. A PDF from Design is a print page, not a press-ready file with marks and a color profile.
Settle three things with a printer before you send anything: the sheet size, the bleed and the color. The design has to be laid out at the sheet size, only a flipbook can carry bleed, and the output is RGB while the press isn't.
If the job is packaging, the dieline is the fourth thing: a flat outline of the pack with its fold lines, which the artwork has to sit inside. The steps are in Recipe 9.
Sharing and collaboration
The Share icon in the top bar opens two kinds of access and a role for each person you invite.
Anyone with the link makes the project public: the design, its source files and its version history open to whoever has the URL, with no sign-in. Restricted keeps it to people you invite by email. Everyone you invite gets Viewer or Editor, and the role decides whether they can change the design or only read it. Manager appears only where your own sharing role can grant it, and a Hub project doesn't offer Editor, because the Hub already gives edit access.
Just the design and The whole process decide which link you copy, and the page selector narrows it to some of the pages. Only the link changes, not who can open it.
Viewing is open to anyone with a public link. Downloading from it isn't: a viewer's download follows what their own account can download, which is why a link that works for your colleague can still refuse a file for someone else.
Set General access to Restricted to stop public-link access. People already invited, or with access through the project's Hub, may still open it. Remove those permissions separately when necessary.
Duplicate and Remix both make a copy, and they differ in one way. Duplicate copies the project, its files and its conversations, so a teammate gets the same design with the discussion attached. Remix gives you an editable copy of a shared design to work from, which is what you want when the point is a fresh start from someone else's look.
GitHub follows the person. In a shared project, each person's own GitHub connection is used for the agent's GitHub work. Sharing a project doesn't share your repository access, and someone without a connection sees the file work they're allowed to see, not yours.
Add to Hub puts the project into your Hub, the shared team workspace.
The roles are coarse. Owner is the person the project belongs to. Viewer reads the design, and can Remix it into their own account. Editor changes the design. Choose the role before you send the invite.
Review is what sharing is built for. Pins never leave the browser that made them, so the notes come back to you outside the project. Duplicate it, then send the agreed changes from one account. Recipe 11 walks through it.
Build it and publishing
Build it sends the design as it stands to a new project in Genspark Code. Pick Website or App: Website sets up a Cloudflare Pages project, and App sets up a Flutter project. The handoff is a README the agent writes for that target. While it writes, the button reads Preparing handoff for {target}...; when it finishes, Your developer handoff is ready appears with Go to Genspark Code, or Open Build ({target}), and that opens the new project in a new tab.
In the new Genspark Code project, review the prefilled request and send it to start the build. Test the result before publishing.
Design makes the design. Genspark Code builds and runs it. Publishing and custom domains happen on the Code side, under the Publish tab, and while it publishes it shows Publishing to Genspark Hosting.
Build it sits in the top bar next to Download, and it's available on every plan, including to a Viewer: it copies the design into their own account first. Starting the project needs credits like any other run. Publishing is the step with a plan behind it: publishing to Genspark Hosting needs Plus, Pro, Team or Enterprise, and Go isn't included. App release builds also need Plus.
Use it when the design is a page someone visits: a marketing page, a portfolio, a small app front end. Build it, open the result, and check it on a phone before you send it around.
Treat each handoff as one-way: the canvas keeps the design and the Code project becomes the thing that runs. A page that will keep changing visually should stay in Design longer; one whose content is settled is ready to hand over.
Design Build it
Troubleshooting
Find your symptom below. The ones that need more than a line are written out under the table.
| What you see | What to do |
|---|---|
| The Tweaks panel is empty | Say "make this tweakable" in the chat and the agent generates controls |
| Build it is grayed out | It's grayed out while the agent is still working, and while a handoff is being prepared. The tooltip says Wait for the current agent turn to finish, then try again. |
| It generated something I didn't ask for | Add the design type, the size, the audience and the style. Attach a reference screenshot. Point at the exact block with Comment or Draw |
| My edit changed parts I didn't touch | The change went through a redraw. Duplicate the project, then make one narrower request. Editing and edit safety |
| It changed the wrong page or the wrong image | Wrong page or image |
| A run fails, freezes, or comes back blank | Run problems |
| The project is blank or gone after a refresh | Project blank or gone |
| The design looks plain | Plain-looking output |
| An export is missing, blank, or won't open | Export problems |
| The export doesn't match the canvas | Export differences |
| I was charged more than I expected | Images beyond the default model at default quality, video and the image tools bill credits on top of a turn, and every retry is a new generation. What bills credits |
| I ran out of credits mid-design | Open Credits in the account menu, then Add credits on the Credit Usage History page, and send the request again. Credits and costs shows where it went |
| The design came out in the wrong language | Wrong language |
| I can't find a design | My Designs on the Design home page. Projects deleted from there don't come back |
| Someone can't open my share link | The project is Restricted. Sharing and collaboration |
| Someone can open my link but can't download the file | Their download follows their own account, not the link. Who can see a design I share? |
| My print file is the wrong size | Print size and paper |
| Build it didn't open a project | Wait for the agent to finish, then click Go to Genspark Code. Handoff problems |
Runs
A run failed, froze, or came back blank
Work through these in order.
- Reload the project. The canvas can lag behind the chat, so a run that looks frozen may already have finished.
- Check the chat for a question. A run that's waiting on an answer looks like a run that stopped. Answer in the same conversation and it carries on.
- Ask again. A second attempt is a new generation, and it usually clears a stuck render.
- Duplicate the project before you retry if the version on the canvas is one you want to keep.
- Report it with the project link if it fails the same way twice. How do I report a problem? has the steps.
A failure that produced nothing is returned automatically, up to a daily limit, but a retry is a new run and uses credits. A run you stopped yourself is charged. Refunds has the rest.
The handoff didn't open a project
Wait for the agent to finish. Build it stays on Preparing handoff for {target}... until the README is written.
Click Go to Genspark Code, or Open Build ({target}). It opens in a new tab, so allow pop-ups for Genspark if nothing appears.
If the button stays on Preparing, click x (Cancel handoff) and try again.
If the new tab says Quota exceeded. Please upgrade your plan to continue., the project can't start because the account is out of credits. Credits and costs has where they went.
The project is blank or gone after a refresh
Reload once. A canvas that came back empty is sometimes a view that hasn't caught up with the conversation.
Open the project again from My Designs, not from a browser tab you kept. The gallery is the list of what exists.
Read the last messages in the chat panel. If the agent is waiting on an answer, the canvas stays as it was until you give one.
Wait for the task list to clear if a generation is still running. A canvas can be empty for the length of a build and fill at the end.
Report it with the project link if the project is missing from My Designs as well.
A project deleted from My Designs doesn't come back, and its conversation and versions go with it. With the organization lock on, a delete is refused instead.
Editing and the result
It changed the wrong page or the wrong image
Check which element you actually named. "The hero image" and "the image at the top of the second page" are different requests, and a design with several similar blocks invites the wrong one.
Point at the block. Pin a Comment on the block that should change, or draw an arrow at it with Draw, then send.
Say what stays. "Change only the headline on page two, leave page one and the images alone" gives the agent a boundary it can hold.
Compare the result against your duplicate to see what moved, then ask for the part that moved.
Duplicate the project before a corrective redraw if the version on the canvas is one you want to keep.
A redraw that hits the wrong block usually happens because the instruction was positional ("the section below the quotes") on a page where the position is ambiguous, or because the change was sent as a whole-page request. Both are fixed in the prompt. Why did other parts of my design change when I asked for one edit? explains the mechanism.
The design looks plain
Attach a Design System, so the palette, the type and the components are decided before the first generation.
Attach a reference: a screenshot of a layout you like, or a Figma frame with the spacing you want.
Put the style, the audience and one visual direction in the prompt. "Clean" and "modern" describe nothing the agent can act on; "editorial, one large photograph, generous white space, two colors" describes a page.
Replace placeholder imagery with a real photograph. Attach the file and say to use it as it is.
Refine one element at a time from there. Details in How do I get better-looking output?.
Plain output is usually a thin brief. The agent fills gaps with safe choices, and every fix above removes a gap.
Export and print
An export is missing, blank, or won't open
If it isn't in the menu, the format you want may belong to a different design type. PNG and PSD come from the Export menu, which appears when the page is built as a poster, and MP4 comes from Export video.
If the PDF is blank or the pop-up never appears, the browser is printing it. Allow pop-ups, or use the link in the chat.
If a download prompt appears, see When a download is limited.
If Adobe can't open the PSD, some layer effects didn't rasterize, so the file can be thinner than the design looks. Rebuild the missing layer in Photoshop.
For anything the product doesn't cover, the Troubleshooting Guide has the wider list.
The export doesn't match the canvas
If the PPTX lost the gradients, filters or shadows, complex styling changed during conversion. Ask for screenshot-based slides if the look matters more. Is the PowerPoint file editable? has the trade.
If the PDF came out with white where the design had color, turn on background graphics in the print dialog. It's off by default in most browsers.
If the PDF is a different size, the page size came from the print dialog. Print size and paper.
If the PNG is soft at large sizes, check its resolution before enlarging it for print. It's rendered at three times the canvas size, and it's still a raster image.
If the text reflowed, a font the browser or PowerPoint couldn't find was replaced, and the line breaks moved with it.
Check one page before you export the set. A single-page export at the real destination, such as a PDF opened in the browser's viewer or a PPTX opened in PowerPoint, tells you in a minute which of these you're looking at. The fix is usually in the export settings, not in the design.
Language
The design came out in the wrong language
Design follows the language of your prompt, not the language of the interface, so a design asked for in English comes back in English on a Japanese account.
Text the agent reads can pull it the other way. A document, a URL or a template in another language is content it copies, and copied text arrives in its own language. Attach an English brief and a Japanese reference, and part of the result can land in Japanese.
The fix is in the prompt: write it in the target language, and add one line that leaves nothing to infer. "All text in Japanese" is a stronger instruction than the language the brief is written in. The same line works on a design you already have: ask for the text to be rewritten in that language and the layout left alone.
FAQ
Making and starting
Do I need Genspark Code to put a website live?
You need a Genspark Code project, and Build it makes one for you from the design: pick Website or App, wait for the handoff, then Go to Genspark Code. In the new project, review the prefilled request and send it to start the build, then test the result. Publishing from there needs Plus, Pro, Team or Enterprise, and Go isn't included. More in Build it and publishing.
Why does the agent ask questions before it starts?
A short brief leaves gaps, and a wrong guess means a redraw. Answer the ones that matter and send, and it fills in the rest. Putting the type, size, audience and style in the first message usually removes the round entirely, which is also the cheaper habit.
Can I change the design type after it's built?
Not with a switch. The type is set by the first request and it decides the page size and the export options. Ask for a rebuild in the type you want, or start a new design and attach the old one as a reference.
Editing
I want to undo a change.
There's no one-click undo. Details in Editing and edit safety: duplicate the project before a change you're unsure about, and make one change at a time.
Can I edit a design without the AI regenerating it?
Yes, for text, color, spacing and the other Tweaks values. Click the element with Edit or move a slider, and the change writes straight in with no generation and no charge. Layout, structure and new elements go through the agent as a redraw.
Why did other parts of my design change when I asked for one edit?
A layout or structure change is sent to the agent as a prompt, so it rebuilds that part of the page and can move what's around it. Text and style changes are applied directly and don't. Naming the element and the one change keeps more of the rest in place.
How do I get better-looking output?
Attach a Design System so the palette and type are decided for you, and attach a reference image or a Figma file so the agent has something to match. Say the type, the size, the style and the audience in the first message, then refine one element at a time. Pointing with Comment or Draw gets closer than describing a block in words.
Can I keep two versions side by side?
Duplicate the project and work on the copy. Duplicate keeps the files and the conversation, so either copy is complete on its own.
Can I edit photos in Genspark Design?
Photo editing happens in Media Studio. Design builds a layout around a photo you attach. Recipe 14 shows how.
Design isn't a retouching tool, and there's no upload-a-photo-and-edit-it surface. You bring a finished image into a design and lay out around it, with the photograph placed as it is. The one exception is a poster's layers. When the page is a poster, the Layers panel carries a pencil on each image layer (not shown to a Viewer), which opens Draw to Edit, Remove Background, Erase, Expand, Image Unblur and Image to Video for that layer only. For any other change to the image, such as a color correction, use Media Studio and bring the edited file back into Design with +.
Credits and plans
Is Design covered by Free Quota?
On Plus, Pro and Go, a Standard turn draws on your plan's Free Quota. Ultra turns use credits. A Team or Enterprise seat doesn't currently include Free Quota; a personal Plus, Pro or Go plan still applies its own.
I was charged for edits I didn't keep. Why?
Each redraw is a generation whether or not you keep the result, and a retry is a new run that uses credits. If a run fails on a system error, or ends without producing anything, its credits come back automatically, up to a daily limit. Refunds has the detail.
Can I use my designs commercially?
Commercial use depends on your plan and the Genspark terms. Membership Plans has what each plan allows.
How do I see what Design has used?
Open Credits in the account menu, then find the Design rows in Credit Usage History. The Credits Guide explains how credits are counted.
Is there a Design promotion on my plan?
Design has no promotion of its own: Standard turns use Free Quota where your plan has it, and everything else bills at the normal rate.
Exporting and files
Is the PowerPoint file editable?
Ask for editable PPTX when you need to change text and shapes; complex styling may change during conversion. For closer visual fidelity, ask for screenshot-based slides, whose individual elements aren't editable.
Can the code from Build it go straight to production?
Build it hands the design to a new Genspark Code project, and that project is what runs and deploys. Have a developer read it before it carries real traffic, and keep working on it in Code, not on the Design canvas. See Build it and publishing.
Can I get a vector file?
The files Design makes are raster and slide formats: PNG, layered PSD, MP4, PPTX, PDF and the project ZIP. There's no SVG, Illustrator or EPS export. A printer who needs vector artwork will need it drawn elsewhere.
Can I print the PDF at an exact size?
Print options depend on the design type. A flipbook can carry an exact paper size, bleed and crop marks, so ask the agent to configure them, then verify the PDF dimensions and your printer's requirements. Everything else prints through your browser, where the dialog sets the paper size. Print size and paper.
What's in the ZIP?
The project's source files, which is what a developer needs to work on the page outside Design and what an archive needs to keep the whole thing. It's the whole project, not one page, and it isn't the same file as a PNG or a PDF.
Sharing and access
Who can see a design I share?
Anyone holding a public link can open the design, its source files and its version history without signing in. Restricted limits it to the people you invite. What does a public link expose? has the detail.
What does a public link expose?
The design, its source files and its version history, to anyone with the URL and no sign-in. That's the whole project rather than the single page you were looking at when you copied the link.
That matters in two situations. A client review doesn't need the source files, so Restricted with named invites is the smaller surface: a review that only needs to look can stay Viewer, and anyone who has to change the design is Editor. And a design built over client material, such as an unreleased product photo or a price list, shouldn't sit behind a public link at all, because the files behind the design are as reachable as the design.
Set General access to Restricted to stop public-link access. People already invited, or with access through the project's Hub, may still open it, so remove those permissions separately when necessary. There's no per-link expiry, so a link you sent in an email lives until you change the access.
What's the difference between Duplicate and Remix?
Duplicate copies the project with its files and conversation, and it's free. Remix gives you an editable copy of a shared design, which is also how a Viewer takes the design into their own account. Use Duplicate to hand work on, and Remix to start from someone else's look.
Why can't I delete a project?
Your organization may have locked project deletion. When the lock is on, the delete option is refused and the project stays, including the project behind a Design System. Ask your org admin. More in Where your designs are saved.
How do I report a problem?
Open the project, click Share, invite [email protected] as a Viewer, and send the link with what you asked for and what happened. The project link is what makes the report actionable.
Recipes
Recipe 1 is the edit loop. Recipes 2 to 7 are the six most common jobs.
The edit loop
1. Change one thing without disturbing the rest
For: a design that's close, where one part is wrong and the rest should stay exactly as it is.
Prepare: the project as it stands, and one sentence that names the part that's wrong. If you're unsure about the change, take a duplicate first.
Text and color change in place. Everything else goes back through the agent, and the agent rebuilds more than the part you named. The loop below is the one that keeps a finished design intact.
Steps:
- Duplicate the project from its menu if the version on the canvas matters, because the copy is the only way back.
- Use the direct path for text and color. Click the element with Edit, or move a Tweaks slider. No generation, no charge.
- Describe anything else in one narrow sentence. Name the element, name what stays. "Move the pricing table below the quotes and leave everything above it alone."
- Point, don't describe when there's more than one note. Comment pins them, Draw circles them, and both go in one message.
- Check the result before the next request. A bad redraw that gets built on costs more than one you catch.
Move the pricing table directly under the customer quotes and leave everything above it exactly as it is. Don't change the headline, the images or the spacing between sections.
You get: one changed area and the rest of the page where you left it. A layout change can't be pinned to a single element, so if a redraw takes out something you wanted, duplicate and ask for only the missing part.
Design Edit
If it stalls: the change lands but something else moves with it. Compare the result against your duplicate, then send a request about the part that moved on its own. Restating the whole page resets the work the first request did.
Related: Editing and edit safety for why a redraw rebuilds more than the element you named.
Pages, posters and decks
2. A website or landing page, then Build it, then publish
For: a page someone visits. A launch, a portfolio, a service page for a small business.
Prepare: the offer in one sentence, the sections in order, and one reference: a screenshot, a Figma frame or a Design System. If the copy is already written, attach the document it lives in.
Steps:
- Open a new Design project and pick Standard or Ultra in the selector. A long page is a long run, so Standard is the cheaper place to explore and Ultra is where the final pass belongs.
- Attach the reference with +, or select a Design System beside the prompt input so the palette and type are set before the first generation.
- Send the prompt. Answer the questions about desktop and phone, and let the style ones default if the direction is already clear.
- Fix the words on the canvas with Edit. Headlines and body copy are text elements, so they change without a redraw.
- Check it as a page: Present opens it in a new tab for presenting.
- Take it out. Build it → Website, wait for the handoff README, then Go to Genspark Code. Publishing happens there.
- In the new project, review the prefilled request and send it to start the build. Test the result before publishing.
A dark editorial portfolio site for [a freelance photographer], aimed at prospective clients. Five sections in this order: hero with one large photograph, selected work, about, pricing, contact. Warm serif headings, near-black background. Desktop first, then the phone version.
You get: a landing page on the canvas, a Present view, a share link, and a handoff README with the project opened in a new tab. The publish step has a plan behind it. Build it and publishing covers which.
If it stalls: Build it is grayed out while the agent is still working, or while a handoff is being prepared. Wait for the turn to finish, then click again.
Related: Recipe 4 if the page's content is really a deck, and Design or another tool if you're deciding between Design and a website builder.
3. A poster or flyer, then PNG, PDF or PSD
For: an event, a promotion, a print piece that leaves the screen.
Prepare: the date, the venue, the price, the logo and any photograph. Decide the sheet size before you send, because the design is laid out at it.
Steps:
- Ask for a poster and give it the sheet size, the hierarchy and the color direction in the same message.
- Attach the logo and the photograph with +. A real logo file keeps the mark exact.
- Set the copy directly. Prices, dates and addresses are text, so Edit fixes a typo without touching the layout.
- Export from the Export menu: Export image for a PNG, Export PSD for a layered Photoshop file.
- For a PDF, ask for "export as PDF" in the chat and print it from the browser with background graphics on.
A4 portrait flyer: professional charity gala dinner with an elegant black and gold theme, featuring event details, keynote speaker name, and venue information at [The Grand Ballroom].
You get: a PNG for screens, a layered PSD for a designer, and a PDF from your browser's print dialog. The sheet size and margins are what you set there.
If it stalls: an export that isn't in the Export menu usually means the design isn't a poster. An export is missing, blank, or won't open has the rest.
Related: Print size and paper before a print run, and Recipe 6 when the same poster has to work at three sizes.
4. A slide deck, then PPTX or PDF
For: a pitch, a report, a training deck that has to match a brand.
Prepare: the outline, one idea per slide, and the numbers you need to show. Attaching a Design System at the start is cheaper than restyling twelve slides at the end.
Steps:
- Ask for a deck with the slide count, the audience and the point of the closing slide.
- Select the Design System beside the prompt input so the deck matches everything else in the brand.
- Work one slide at a time. Ask for the slide that's wrong, not the whole deck.
- Present it with the arrow keys, and check the Speaker Notes on a deck that has them.
- Export PPTX if people will edit it, and a PDF if the look has to be exact.
A 12-slide deck for a Series A pitch to investors who already know the category. One idea per slide, a chart placeholder where the numbers go, and a closing slide with the ask. Use our Design System, and speaker notes on every slide.
You get: a deck you can present, a PPTX people can edit, and a PDF for sending. Is the PowerPoint file editable? covers what survives the PPTX conversion.
If it stalls: a slide that comes back redesigned, not edited, went through a redraw of more than that slide. Ask for the one element instead. For a pure presentation with its own slide editor, AI Slides may suit you better.
Related: Design or another tool for the Design and AI Slides decision.
Prototypes and sets
5. A clickable prototype, then Present and share
For: showing a flow to a stakeholder or a developer before anything is built.
Prepare: the screens in order, what each one does, and a Figma frame if the visual language already exists. Write the back path down too, because it's the part a brief usually leaves out.
Steps:
- List the screens in the order they run. A prototype with an unstated flow comes back with the obvious one.
- Attach the Figma file if the look is settled. The frame's spacing and type carry into the generation.
- Ask for each screen to link to the next, and say what the back path is.
- Click through it with Present. A flow that reads well as pictures can still break on the second screen.
- Duplicate the project, then share it Restricted and collect the feedback outside Design. One editor sends the agreed changes.
- Hand it on with the share link, or Build it if the flow has to run as an app.
A clickable prototype for a booking page for a small gym: home with today's classes, a class list, a class detail with a book button, and a confirmation. Each screen links to the next, and every screen has a way back. Clean and calm, one accent color.
You get: linked screens you present in a new tab, and a link a reviewer can click through.
Design Logo
If it stalls: a screen that won't advance usually means the link wasn't built. Ask for that one link in the chat, naming both screens.
Related: Recipe 11 when more than one person has to sign the flow off.
6. A social set from one brief
For: one announcement that has to work on a feed, a story and a banner without three separate designs.
Prepare: the announcement in one line, the sizes you need, the product shot and the brand. Write the sizes as ratios so the brief is unambiguous.
Steps:
- Ask for the first size as a poster, so it gets the PNG export. Square for a feed, 9:16 for a story, a wide banner for a page.
- Approve one direction before the rest. Extending one direction costs less than extending five.
- Ask for the other sizes from the same design, naming the ratio, with the artwork attached.
- Change the copy per size with Edit when a headline has to be shorter on the story.
- Export each one as a PNG and check the first at full size before you send the set on.
Poster for a B2B SaaS product launch announcement, aimed at founders on LinkedIn. One headline, one supporting line, the product name, our colors. Make it square first, then the same design at 9:16 for Stories and a 16:9 banner.
You get: one design in three sizes, as PNGs for posting.
If it stalls: a resize that comes back as a new design means the original wasn't attached. Attach it and ask again.
Related: Recipe 3 for the single-size version, and Habits that keep spend down before you ask for ten variants.
Brand, print and motion
7. A logo and brand kit, saved as a Design System
For: a new brand that has to hold together across a site, a deck and a poster.
Prepare: the name, one line on what the business does, two or three colors you like, and three references. Have the logo file itself if the mark already exists.
Steps:
- Ask for three logo directions, not one, and say where the mark will be used: a favicon, the corner of a deck, a profile image.
- Pick one and refine it with Edit, changing the color and the type, not re-prompting the whole mark.
- Save the brand as a Design System: Design System below the input box → Create New, then describe the brand and import the logo file.
- Review the extracted palette, type and components, then confirm them against the real brand values.
- Select it in every new project with the Design System selector beside the prompt input.
A logo for [name], a neighborhood bakery. Warm and handmade, not corporate: a wordmark with a small illustrated mark, two colors, works on a paper bag and on a phone screen. Show me three directions.
If a design already has the look right, save the system from it instead: Share → Create design system from this project.
You get: a logo on the canvas and a saved Design System that applies to every later project in the brand. For a PNG or a layered PSD of the logo, build it as a poster so the Export menu appears.
If it stalls: if the system keeps losing a color, open it and check the palette. Design System has the rest.
Related: Recipe 2 and Recipe 3 are the two jobs the system pays for first.
Design Logo
The rest, in full
8. A business card or another print asset
For: a card, a letterhead, an invoice sheet, or a one-sided flyer: anything that goes to a printer at a fixed size.
Prepare: the trim size (a business card is 3.5 by 2 inches), both sides' content, the logo file, and the colors from your Design System if you have one.
Steps:
- Say the trim size in the prompt and name it as inches or millimeters. A card described only as "a business card" can come back at a different proportion.
- Attach the logo with +, and attach the Design System so the type and colors are decided before the first pass.
- Ask for the front and the back as two pages, not one image with both halves.
- Set the name, the phone number and the address with Edit. Contact details are the part that's always wrong on a first pass, and they're cheap to fix directly.
- Keep everything you need printed inside the page. Design has no bleed or safe-zone setting, so a card that runs to the edge will print with no bleed.
- Export a PDF as a proof, and ask your printer what file they need. A PSD is for a designer who will finish the file.
A business card for [name], a landscape architect. Front: logo and name. Back: phone, email and site, aligned left. 3.5 by 2 inches, off-white, one deep green. Show the front and the back as two pages.
You get: a two-page design at the size you named, a PDF you can send as a proof, and a PSD if the printer wants a layered file.
If it stalls: the printer asks for bleed or crop marks, and Design doesn't produce them. Ask the printer for their smallest acceptable margin instead, and rebuild the card with the artwork pulled inside it.
Related: Print size and paper for what a print page does and doesn't carry.
9. Packaging on a dieline
For: artwork that has to sit on a box, a bag or a sleeve.
Prepare: your printer's dieline (the flat outline of the pack with its fold lines), the flat size, and what goes on each panel.
Steps:
- Ask for artwork at the pack's flat size and describe what goes on each panel, one panel per instruction.
- Attach a picture of the dieline with + if it helps the agent see the panel layout, and say which line is a fold. It's a reference, not a template the design snaps to.
- Keep all type clear of the folds, and check the folds against your printer's dieline before you order.
- Export a PDF as a proof and send it to the printer for a physical check before the run.
Artwork for a single-origin coffee bag, flat size [width] by [height]. Front panel: origin, roast and a small illustration. Back: brewing notes and weight. Keep all text clear of the fold lines.
You get: a flat artwork page at the pack size, and a PDF proof to check with your printer.
If it stalls: the panels don't line up with the dieline. Send the panel map as a list in the prompt, not the pack in a sentence, and ask for one panel at a time.
Related: Print size and paper for the design types that carry bleed.
10. A logo animation or a short product intro
For: a mark that draws on, a product that turns once, a few seconds of motion for a launch page or a feed.
Prepare: the logo file or the product image, the length in seconds, the one thing it ends on, and the background color.
Steps:
- Attach the mark or the product image with +. A frame movie built from a real file keeps the shape exact.
- Ask for a frame movie and give it the length in seconds and the ending. A frame movie is the one video shape Design builds, and it exports as MP4.
- Say what happens in the middle: the draw-on, the fade, the hold. One beat is enough for four seconds.
- Watch it in the canvas before you export, twice. Motion that reads well once can flicker on the second pass.
- Export the MP4 from Export video.
A 12-second frame movie from this logo: the mark draws on, the wordmark fades in under it, then hold on a dark background with the tagline "[line]".
You get: an MP4 clip at the length you asked for, built from your own mark.
If it stalls: the clip comes back longer or shorter than you asked. Put the seconds in the first line of the prompt, not at the end, and say "exactly" with the number.
Related: Media Studio for anything with live footage, cuts or a soundtrack.
11. A review round
For: a design that needs sign-off from two or three people before it goes anywhere.
Prepare: the finished design, the names of the people reviewing, and one sentence on what you're asking them to decide.
Steps:
- Set the project to Restricted in the Share dialog. A public link exposes the source files and the version history as well as the design.
- Duplicate the project before the round, so there's a copy to fall back on. A redraw while the notes are still coming in makes them describe a design that no longer exists.
- Collect the feedback outside Design: a call, a document, a marked-up screenshot, one thread per reviewer.
- Reconcile the notes into one list: one line per change, and the order to apply them in.
- Send the list from one account, as a single message, with the changes named in the order you want them.
Here are the reviewer notes: [paste]. Make only these changes, one at a time, and leave everything else as it is.
You get: one revision pass that reflects the notes you agreed on.
If it stalls: two reviewers contradict each other. Decide which note wins before you send the prompt, because an instruction that contains both comes back with one of them applied at random.
Related: What does a public link expose? before you send any link outside the team.
12. A flipbook, catalog or lookbook
For: a set of products or pages that has to read as a document: a catalog, a lookbook, a short brochure.
Prepare: the page size, the exact page count, one item per page, and the images with their names or prices.
Steps:
- Ask for a flipbook or paged book, and give the page size and the exact page count in the first line. If the printer needs bleed and crop marks, ask for them in this message, for example 3 mm bleed with crop marks.
- Say one item per page and give the order. A catalog with an unstated order comes back alphabetized or in the order you happened to list things.
- Attach the images with + as a set, and name which image goes on which page in the prompt.
- Check the first three pages in Present before you look at the rest. A wrong page size or a wrong item order repeats on every page after it.
- Fix prices and names with Edit, then export a PDF through the print dialog.
A 12-page lookbook for a ceramics studio, A4 portrait. One piece per page: a photograph, the name, the dimensions and the price. Keep the type small and let the photograph take the page.
You get: a multi-page document that reads as pages, a Present view that flips through it, and a PDF from your browser's print dialog.
If it stalls: the page count is wrong, or the last page is half empty. Give the count and the exact number of items in the same sentence. A 12-page book with 11 items always leaves one page to fill.
Related: Print size and paper.
13. A wireframe first
For: a screen whose structure isn't settled, where arguing about layout before styling saves a rebuild.
Prepare: the screens, what each one has to do, and the order they run in. No brand, no colors.
Steps:
- Ask for a low-fidelity wireframe and say what it's for: structure, decisions, no styling.
- Keep the request plain. Gray boxes, labels and the blocks each screen needs are enough, and asking for "a nice looking wireframe" defeats the point.
- Review the structure with the person who has to agree to it, and change it while it's still cheap.
- Attach the wireframe and ask for the full design from it, so the layout you agreed to is the layout that gets styled.
A low-fidelity wireframe for a booking app for a small gym: home, class list, class detail, confirmation. Gray boxes and labels, no brand.
You get: a structural page you can show someone without them commenting on the colors, and a full design built from it in a second pass.
If it stalls: the wireframe comes back styled. Say "no color, no logo, gray boxes and labels" in the prompt, and treat any color as a sign the brief needs the word wireframe earlier in it.
Related: Recipe 5 once the structure is settled and the screens have to link.
14. A page built around a photo you already have
For: a photograph that's already right (a product shot, a portrait, a room) and a page that has to be built around it.
Prepare: the image, the page size, and the copy that goes with it. If the image itself needs work, do that first in Media Studio.
Steps:
- Do the photo work first, in Media Studio. Design lays out a page around an image; it doesn't retouch one.
- Attach the finished image with + and say to use it as it is. Without that line, the agent may generate its own image and not place yours.
- Describe the layout in terms of the image: where it sits, how much of the page it takes, and where the text goes around it.
- Keep the type off the busy part of the photograph, and check the contrast where text sits over it.
- Export as a poster PNG if the page is a single sheet, or build the page out with Build it if it's a web page.
Use the attached photograph as it is, don't regenerate it. Build a product page around it with the image large at the top, the product name and price under it, and one short paragraph of description. Clean, mostly white, one accent color.
You get: a page built around your own image, with the photograph placed as it is.
If it stalls: the design comes back with a different image. Say again, in the first line, that the attached photograph is the final artwork and must not be regenerated.
Related: Can I edit photos in Genspark Design? for the boundary between the two products.
Related articles
- Credits Guide for how credits are counted and spent.
- Membership Plans for what each plan includes.
- Media Studio for video ads, photo edits and 3D.
- AI Slides for presentations.
- AI Drive for the files you attach.
- Troubleshooting Guide for problems that aren't Design-specific.
- Genspark Code for coding work in a developer environment.
Genspark Design is its own canvas. The UI Designer and Graphic Designer agents in GenTeam are separate roles with their own tools.