Skip to main content
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.
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.

Website Tab

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.

Prompt Tab

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.
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:

​
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.
Prompt Skeleton Template

​
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.
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).
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.
  • 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

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

​
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