> ## Documentation Index
> Fetch the complete documentation index at: https://docs.demokraft.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Getting Great Results from Prompt a Studio & Prompt a Motion
> A practical guide to writing inputs—URLs or text prompts—that produce publish-ready product and motion videos.
A practical guide to writing the input—a website URL or a written prompt—that produces a video you'd actually publish.
This is a **how to give good input** guide.
***
## 1. Which option should I use?
Both options sit on the Demokraft AI Portal Home page and take exactly the same two kinds of input. What differs is what gets built.
| Feature | **Prompt a Studio** | **Prompt a Motion** |
| :------------------- | :----------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
| **What you get** | A scene-based product video assembled from DemoKraft's scene templates—your screenshots, logo, and photos placed into layouts. | A **motion-graphics** video—animated headlines, counters, icon flows, abstract product-UI cards, all moving smoothly. |
| **Best for** | Custom, reusable, highly controlled content | Fast, polished video creation |
| **Creative control** | High | Focused on outline/storyboard approval |
| **Editing** | Fully editable Studio project | Designed for fast generation |
| **Voice** | Scripts are written for you; **you generate the voice yourself** in the editor. | **Narration is generated during the build** with the voice you pick before hitting Generate. |
| **Music** | You add it in the editor. | You pick the track (or upload your own) before hitting Generate. |
| **After it's built** | Fully editable in the Studio editor—scripts, effects, backgrounds, everything. | Captions and Export stay open; changes are made by **typing feedback** in the editor's Feedback panel (3 rounds). |
**Rule of thumb:** **Prompt a Motion** is ideal when speed and simplicity matter more than extensive hands-on editing. **Prompt a Studio** is ideal when you need full creative control and an editable project.
***
## 2. Website tab or Prompt tab?
Both options give you the same two tabs. Pick the one where your best information actually lives.
**Use when:** Your product site is public, loads without a login, matches your intended brand theme, and clearly states what the product is, who it's for, what problem it solves, and key benefits.
*The app automatically extracts copy, headings, colors, fonts, and images from the page.*
**Use when:**
* Product is unlaunched or behind a login/waitlist.
* Site undersells the feature you want to feature (e.g. you're launching one new feature and the homepage is a general overview).
* Site is image-heavy with minimal text.
* You want tight control over wording and emphasis.
* Creating a specific feature, release, or concept video.
**Attaching Images:** You can attach images on either tab. On the Website tab, attached images are used *alongside* scraped web assets—handy for uploading a cleaner logo or a screen that isn't public yet.
**Nothing is invented.** The video will not claim a price, a guarantee, an integration, a customer count, or a capability you didn't state. A thin input produces a shorter, plainer video—not a padded one. If you want it on screen, say it.
***
## 3. The Nine Core Input Elements
Whichever tab you use, the system extracts these key elements. Every item you supply is one less detail left blank.
| # | What to state | What it becomes |
| :---- | :---------------------------------------------- | :------------------------------------------------------- |
| **1** | **Product name** + one-line **tagline** | Opening and closing scenes, spoken and on screen |
| **2** | **What it actually does** (in plain words) | The spine of the entire narrative |
| **3** | **Who it's for** | The vocabulary and tone of every line of narration |
| **4** | **The purpose of *this* video** | Which story gets told—an overview, a launch, or an intro |
| **5** | **The problem** it removes | The opening beat; without it, the video starts flat |
| **6** | **3–5 benefits** (outcomes, not features) | The middle scenes—roughly one core idea per scene |
| **7** | **Proof: numbers, steps, quotes, integrations** | Unlocks high-value scene types (see Section 5) |
| **8** | **Call to Action (CTA)** + URL | The closing scene |
| **9** | **Brand colors and font** *(optional)* | Essential for custom brand themes in the Prompt tab |
**Image Labeling:** If you attach images, state what each file is—especially which file is your logo!
### Focus on Outcomes, Not Features
Write the business or user outcome rather than the technical mechanism:
| ✅ Write This (Outcome) | ❌ Avoid This (Feature) |
| :------------------------------------------------------ | :-------------------------------- |
| "Close the month in an afternoon instead of three days" | "Automated reconciliation engine" |
| "Never send a quote with stale pricing again" | "Real-time pricing sync" |
| "See which deals are slipping before your 1:1" | "Predictive pipeline analytics" |
***
## 4. Writing the Prompt
### The Skeleton Template
Copy this template, fill it in, and delete unused fields. Category labels help the AI parse structure.
Use the **Use sample** or **Copy sample** links above the prompt box in the portal for a pre-filled, editable version.
```text title="Prompt Skeleton Template" theme={null}
Product: — ""
What it is: <2-3 plain sentences. What it does, for whom, and how.>
Purpose of this video:
Target audience:
Tone and emphasis:
The problem:
Key benefits: <3-5 outcomes, one per line or comma-separated>
Proof:
How it works: <2-4 ordered steps, if there's a clear sequence>
Call to action:
Brand guidelines:
Uploaded images: is our logo. is a product screenshot of home page. …
```
### Prompt Length Guidelines
* **Prompt Tab:** 40 characters minimum, 8,000 maximum (live counter active). Below the minimum, the project won't be created.
* **Website Tab (Custom Instructions):** 5,000 characters maximum.
* **Recommended Length:** **800–2,500 characters** (roughly the size of the template above). Shorter inputs result in generic middle scenes; excessively long inputs get trimmed for a 30-second video.
### Where to Put Custom Steering
The **Prompt** tab has no separate instructions box on purpose—say it *inside* the prompt itself (e.g. "Purpose of this video: …", "Tone: …"). On the **Website** tab, that's exactly what the *Custom Instructions* box is for.
**Example steering statements:** "Target investors, not end users." · "Lead with the new scheduling feature, not the whole product." · "Emphasize compliance and data residency." · "brandmark.png is our logo."
***
## 5. Earning High-Impact Scenes
Certain animated scene types are unlocked **only** when your input provides the required raw data.
| Target Scene Type | Required Input Material |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Number Count-Up (Stat Scene)** | Explicit metric with units and context: *"39 languages supported"*, *"4× faster month-end close"*, *"12,000 teams"*. *(A generic "very fast" will not trigger this).* |
| **How-it-Works Flow** | **2–4 ordered steps**: *"Connect your billing tool → we map your data → your forecast updates nightly."* |
| **Before/After Split** | Both states explicitly named: *"Before: three days of spreadsheet surgery. After: a forecast that's current every morning."* |
| **Social Proof / Quote** | The actual testimonial quote and who said it. |
| **Ecosystem / Integrations** | Specific tool names spelled out: *"Stripe, HubSpot, NetSuite."* |
| **Logo Landing** | A logo file attached, with the filename stated in text. *(Fallback: product name as a wordmark).* |
| **Product Screen Showcase** | An attached screenshot (or a public site we can pull one from)—readable, full-window, no half-loaded states. |
| **Strong Closing CTA** | A CTA of about **three words** + URL: *"Start free trial — zephyr.io/trial"*. Long CTAs get trimmed. |
**The pattern:** Specific, checkable facts unlock scenes—adjectives don't. *"Enterprise-grade and blazing fast"* produces one more sentence of narration. *"SOC 2 Type II certified, 99.99% uptime across 2 years"* produces an entire scene.
***
## 6. Image Guidelines
Images are optional on both tabs, but they are the single highest quality lever after prompt text.
1. **Limit & Formats:**
Upload up to **5 files** in `JPG`, `PNG`, `WEBP`, or `SVG` format. Anything else is skipped with a message naming the file. (SVG logos are automatically converted.)
2. **Label Filenames in Text:**
Map filenames in your prompt—filenames are how images get matched to the right role:
`brandmark.svg is our logo. dashboard.png and settings.png are product screenshots. team-photo.jpg is a lifestyle shot.`
3. **Quality Over Quantity:**
Blurry or unreadable images are detected and skipped automatically—so a bad screenshot doesn't get used, it just leaves a gap.
4. **Good Screenshot Hygiene:**
Full window, real (or realistic) data, nothing half-loaded, no browser chrome unless the browser is the point, and no personal customer data.
5. **People vs. Product UI:**
Founder headshots and testimonial avatars are automatically recognized and will not be forced into product frames. Photos of people *using* the product are treated as lifestyle imagery and can be used anywhere.
6. **Missing Images:**
Where a scene needs an image you didn't supply, the system may generate a small number of generic supporting images per project, or fall back to a placeholder you can swap in the editor.
***
## 7. Configuration Pickers
Located next to the **Generate Video** button:
### 1. Duration
**Available options:** 15 / 30 / 45 / 60 / 90 seconds.
*Budget roughly 1 scene per 5 seconds (e.g., 30s ≈ 6 scenes).*
| Content Volume | Recommended Duration |
| ----------------------------------------------- | -------------------- |
| Single message, quick teaser, or feature launch | **15 – 30s** |
| Problem statement + 3 benefits + CTA | **30 – 45s** |
| Comprehensive story with proof and workflow | **60 – 90s** |
Three benefits stretched over 90 seconds gets repetitive; eight benefits crushed into 15 seconds gets nothing said properly. **On the Free Studio plan, the duration list stops at 30 seconds.**
### 2. Video Type
* **Intro:** Brand-first overview (Who we are, what we do, why it matters).
* **Explainer:** The core workhorse (Problem → Solution → How it works → Outcome).
* **Launch:** News-driven focus (What's new, why now, what it unlocks). *Specify what feature is launching in your prompt!*
### 3. Language
* **Current Support:** English only.
* **Upcoming:** Additional language support is coming soon.
***
## 8. Prompt a Motion: Pre-Generation Tips
* **Voice and music are chosen up front.** Below the input box you'll find a voice picker (with preview and a speed control) and a music picker—a library track, your own MP3 (ensure you have copyright permission), or no music. Choose deliberately: narration is synthesized during the build, and a motion project's Script and Music panels are **not editable afterward**.
* **Write for the ear as well as the eye.** Motion scenes carry one idea each, in very few words—a headline of about 8 words, a supporting line of about 14. Short declarative sentences in your prompt translate cleanly; long subordinate-clause paragraphs get compressed, and you have less say over how.
* **Don't over-specify layout.** Asking for "a three-column pricing grid" won't produce one—the motion vocabulary is a fixed set of animated shapes. Describe the *message and the evidence*; the system chooses the shape that carries it.
* **After it's built:** Captions and Export stay available, and the **Feedback** panel (left sidebar) is where all changes happen—see § 10.
***
## 9. Prompt a Studio: Pre-Generation Tips
* **Your images do the heavy lifting.** A real screenshot unlocks device-mockup and before/after scene types that otherwise fall back to placeholders. If you have exactly one good screenshot, attach it.
* **Brand colors come from the source.** On the Website tab, the system reads your site's palette. On the Prompt tab, state your colors and font, or you get the clean default (white background, black text, Afacad).
* **Voice is not generated automatically.** The scripts arrive filled in; open the Script panel, pick a voice, and generate. Everything else in the editor—background, music, effects, captions, timing—is yours to change.
***
## 10. Reviewing & Iterating Storyboards
You receive **two review checkpoints** before final video assembly. Use them to refine content without wasting generation credits.
```text theme={null}
Input Prompt ➔ [ Checkpoint A: Story Direction ] ➔ [ Checkpoint B: Full Storyboard ] ➔ Video Build
```
* **Checkpoint A (Story Direction):** Review scene count and 1-line scene summaries. No visuals yet—this is the moment to fix *what the video is about*.
* **Checkpoint B (Full Storyboard):** Review exact layout, visuals, on-screen copy, and voiceover text. Fix wording, imagery, and emphasis here.
Each checkpoint allows up to **3 revisions**, counted separately. Feedback is free text—keep it under \~2,000 characters.
### Effective Feedback Examples
| ✅ Specific & Actionable | ❌ Vague & Ineffective |
| ---------------------------------------------------------- | --------------------- |
| "Scene 2 should lead with time savings, not integrations." | "Make it better." |
| "Cut Scene 4 and allocate time to the closing CTA." | "It feels too long." |
| "Use dashboard.png screenshot in Scene 3." | "Wrong images." |
| "Replace 'revolutionary' with 'built for finance teams'." | "Tone is off." |
| "Make the intro background calmer." | "Colors are wrong." |
Name the scene number, name the change. One round of three or four precise notes beats three rounds of "hmm, not quite".
**Closing a review window cancels the project.** It doesn't get saved as a draft you can come back to. Approve it, or start again from the Home page.
### After the Build
* **Prompt a Studio:** Everything is editable in the Studio editor.
* **Prompt a Motion:** Use the **Feedback** panel: type what you want changed and the video is recomposed (including re-recording any narration that changed). **3 rounds per project**, up to 5,000 characters each; the editor is blocked with a progress message while a round runs. Scene count is locked once built, so "add a scene about pricing" won't work—that belongs at Checkpoint A.
***
## 11. Pitfalls That Hurt Video Quality
* **Marketing abstraction with nothing underneath.** *"Next-generation AI-powered platform empowering teams to unlock synergies"* gives the system nothing to build a scene from.
* **Feature lists instead of outcomes.** See § 3.
* **No stated problem.** The opening scene falls flat and the whole video reads as a brochure.
* **Unnamed images.** Five attachments and no explanation means guesswork about which is the logo.
* **A URL to a page that isn't about the product**—a blog index, a login page, a pricing table with no context. Point at your homepage or your main product page.
* **Claims you can't back up.** Don't put a number in the prompt unless it's real; it may end up on screen and spoken aloud.
* **Wrong duration for the amount of content.** See § 7.
* **Approving Checkpoint A when the direction is wrong**, hoping to fix it at Checkpoint B. The storyboard is built *from* the direction—fix it upstream.
***
## 12. Troubleshooting
| What you see | What it usually means |
| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "The website could not be accessed (HTTP 403)…" | The site blocks automated access. Use the Prompt tab instead. |
| "Failed to extract product information from the website." | Too little readable text on that page. Try your homepage or main product page, or switch to the Prompt tab. |
| A message asking for more detail | The prompt is under 40 characters. |
| A file was skipped | Unsupported format (only JPG, PNG, WEBP, SVG), or the image was too blurry to use. |
| Generic middle scenes | The input had benefits but no proof—add numbers, steps, or quotes (§ 5). |
| Placeholders where you expected product screens | No usable screenshot was attached or found. Attach one and regenerate. |
| Content refused | The input tripped the content policy. If it's refused at creation, nothing is created and your monthly allowance is untouched. Lawful-but-sensitive industries are fine here; if something legitimate was refused, contact support. |
| "You've reached your limit" | Prompt-a-Video projects are capped per month by plan; usage is shown in **Settings › Billing**. |
| Video duration differs slightly from what you picked | Final video duration can vary a bit based on the voiceover script you approved. |
***
## 13. Pre-Flight Checklist
Before clicking **Generate Video**, verify your input:
* [ ] Product name and 1-line tagline included
* [ ] Concrete problem statement clearly defined
* [ ] 3–5 key benefits expressed as outcomes
* [ ] At least one proof point added (a number with its unit, a sequence of steps, a quote, or named integrations)
* [ ] Video purpose specified (especially for Launch videos)
* [ ] Target audience defined
* [ ] 3-word CTA + URL included
* [ ] Brand hex colors and font specified (if custom theme desired)
* [ ] Images attached and labeled by filename (logo specified)
* [ ] Duration selected matching content volume
* [ ] *(Prompt a Motion only)* Voice previewed, speed set, and music chosen—these are locked in after the build