Draft mode

Draft mode lets users begin work using fewer details or less powerful processing power before committing to a full, resource-intensive run. This functionality supports an efficient, iterative process. Early generations go faster and users spend less compute or credits to get a preview, and users can easily switch to a higher-quality model once ready.

Versions of this pattern can be found across modalities:

  • Image and video generators often generate low-scaled versions for early iterations.
  • Audio generators produce short previews of voices or mixes before rendering the full track.
  • Coding editors surface plans of action or “design mode” previews to show intended steps or rough interfaces before deeper interactivity and integrations are added.
  • Text editors may start with an outline before generating full documents.
  • Presentation generators often default to slide outlines for early confirmation.

Explicit vs. implicit drafting

While some products support an explicit draft mode, others offer a combination of parameters that creates a similar environment without being direct.

Explicit mode is common in visual mediums like image and video. This makes the visible reduction in the quality of the output feel intensional. Draft mode is framed as a positive means of saving time and money in the creative process.

Implicit modes cover a variety of options:

  • Directly decreasing the step count of a generation reducing the quality of the output but is faster and cheaper than a higher-count run. The number of steps reflect the fidelity of the AI’s reasoning on terms of logical loops.
  • Returning a short snippet as a first step of a high quality run for the user to review before expanding so time is not spent on a longer version that is off-base.
  • Writing an outline for an essay or slide deck before producing the full asset.

All of these produce a lesser-fidelity version of the final result but don't give the perception that the AI is not doing its job.

Using model routing for drafting

As automatic model routing becomes more common, users increasingly rely on the system to select the best model for the task and iterative state. Drafting can be accomplished in effect by defaulting to a less powerful alternative until instructed otherwise. This benefits the user by decreasing compute and credit consumption, but not all users will be wise to what is happening behind the scenes. However, less savvy users may be unaware that they can force the AI to use a more powerful model when needed.

Consider introducing this concept during onboarding in an interactive way, demonstrating that less powerful models can be the better tool earlier in the design process or while chatting about a topic before running a more powerful command like deep research.

Design considerations

  • Make drafts explicit. Not everything needs to be labeled drafting mode but users should never be surprised when the system produces a lower-scaled version of what they expect. Whether producing audio snippets instead of full files, outlines instead of documents, or lower quality images, ensure users retain a sense of control and understanding.
  • Make the trade-off explicit. Describe what is reduced in draft mode, for example model tier, steps, resolution, or duration. Pair the label with expected speed and cost so users can decide quickly without guessing.
  • Keep upgrade paths deterministic. Preserve seeds, prompts, and key parameters between draft and final. If the pipeline changes settings, disclose them and let users lock the seed to maintain composition and layout continuity.
  • Design for rapid loops. Draft mode exists to compress iteration time. Keep “upgrade,” “duplicate to final,” and “compare” one click away. Avoid flows that force users to recreate settings to get a comparable final.
  • Prevent accidental downgrades. Never silently route heavy tasks into draft quality. If you auto-switch for performance, surface a clear notice with a one-click override so users retain control.
  • Expose cost controls near commit points. Indicate token, time, or credit impacts right where the user chooses draft versus final. People plan differently when they see the real cost of pressing “Generate.”

Examples

Chronicle produces a draft outline of each slide as a plan of action for the user to confirm before generating the full presentation.
Midjourney draft mode retains the functionality of the full generator but uses a lower scaled model to reduce compute cost for rapid iteration.
Replit gives the option to create a visual preview of a generation to review before committing to running a full application build.
Runway explicitly recommends working with a less powerful model to draft your video before upscaling to the most powerful model.
Synthesia produces a draft video walkthrough from the editing canvas for users to review before exporting. Video animations and dubbing are suppressed in draft mode to decrease processing needs.