Editor’s & Pre-Production Systems Note:
Transparency & Practical Framework Disclosure: This guide details a creator-led production method for transforming pitch decks and script outlines into reviewable shot lists. Claude Slides is a slide generation and presentation feature built within Anthropic’s Artifacts ecosystem. It is an interactive slide deck creation and export tool; it is not a video editor, does not automatically calculate camera blocking, and does not natively generate video files. Constructing a shot list, assigning camera parameters, and moving assets into a video generation pipeline are deliberate creator steps, not automated one-click features of Claude. CrePal is referenced strictly as an illustrative downstream AI Director workspace where creators organize approved scene beats, shot cards, and timeline revisions. This article does not constitute legal or licensing advice.
Source Verification & Ground Truth:
Anthropic Claude Slides & Artifacts Documentation: Verified against Anthropic’s official support documentation (What are Artifacts and how do I use them?), feature overviews (Claude Features: Artifacts), and platform release updates (Claude Product Updates). Official documentation confirms that Claude can generate slide decks directly from text notes, research reports, and chat interactions. Users can edit slides in real time, present directly from the workspace, and export decks to Microsoft PowerPoint (.pptx) or PDF formats. Claude Slides does not natively generate video clips, calculate camera motion vectors, or sync directly with non-linear editing software (NLEs).
CrePal Video Workspace: Documented at CrePal Features as a video-first AI Director framework that coordinates scene-by-scene script breakdowns, shot list drafting, and revision handoffs.
When video creators and marketing teams pitch a commercial campaign, the project usually starts inside a slide deck. You build a clean presentation to pitch client stakeholders, outline the brand story, and align on visual mood.
Then production begins, and communication breaks down.
The director tries to generate video clips directly from the slide deck. But slides are designed for reading, not filming. A slide that says “show product innovation and user delight” does not tell a prompt engineer whether the camera is using a 24mm wide angle, whether the actor is looking left to right, or how many seconds the scene should run. Without a technical shot list, generative video tools produce inconsistent scenes that do not cut together.
The introduction of Claude Slides provides a practical way to solve this pre-production bottleneck.
Built inside Anthropic’s Artifacts workspace, Claude Slides allows creators to generate, revise, and rearrange structured slide decks directly from conversational outlines.
However, a slide deck is an editorial sequence, not a finished film. To move from a deck to actual video generation, you must turn each slide into a concrete shot list with framing, camera movement, and stable tracking IDs.
Here is how to use Claude Slides as a visual storyboard framework and hand an approved shot list over to your video workflow.
Start With a Presentation Outline
A solid video pre-production deck does not begin with visual styling. It begins with clear narrative pacing.
Give Each Slide One Story Beat
The biggest mistake in video planning is cramming three narrative actions onto a single slide. If a slide contains three separate ideas, the team will guess which moment to visualize first.
Enforce a strict structural rule: one slide equals one narrative beat.
- Slide 1: The Frustration (user struggles with existing problem).
- Slide 2: The Discovery (introducing the brand solution).
- Slide 3: The Feature Focus (macro close-up on product hardware).
- Slide 4: The Lifestyle Payoff (user seamlessly enjoying the result).
When you ask Claude to generate a presentation deck from your script, instruct it explicitly: “Format this outline into five distinct narrative beats, allocating exactly one core story action per slide.”
Separate the Viewer Message From Production Detail
A presentation deck must serve two audiences: stakeholders who review the story, and creators who generate the footage.
Keep these two layers distinct inside the slide structure:
- Slide Canvas (Viewer Message): The bold headline, narrative caption, and primary concept visual. This is what clients read during presentation mode to evaluate pacing and tone.
- Speaker Notes (Production Detail): The technical specifications, audio cues, voiceover lines, and asset links. This is where you store framing details without cluttering the visual slide.
Turn the Deck Into a Visual Sequence
Once your narrative outline is generated, use Claude Slides to organize your presentation into a flowing visual sequence.
Map Slide Order to Scenes and Transitions
Use the presentation view in Claude Slides to review your sequence as a moving storyboard. Click through the deck at the intended speed of your commercial:
- Does the transition between Slide 2 and Slide 3 feel abrupt?
- Does Slide 4 introduce a character that was never established in Slide 1?
- Does the visual progression build energy toward the final payoff?
Because Claude Slides allows direct text editing inside the Artifact window, you can reorder slides, adjust headlines, or insert an establishing scene in seconds.
Add Reference Images and Continuity Notes
A visual storyboard requires anchor imagery. While Claude Slides creates clean layouts, you must define the visual boundaries for your video models.
In the speaker notes of each slide, add clear continuity parameters:
- Lighting and Atmosphere: Specify time of day and color grading (e.g., “warm golden hour sunlight, low contrast, soft film grain”).
- Character Anchors: Note specific wardrobe and hair details so characters do not shift between cuts.
- Location Context: Detail architectural textures and background elements to keep the world consistent across shots.
Convert Each Slide Into a Shot List
A slide presents a narrative moment. A shot list turns that moment into specific camera instructions.
Assign Framing, Movement, Duration, and Assets
To translate a slide into camera-ready prompts, break each slide into four technical components:
- Framing (Shot Size): Define camera distance (e.g., Extreme Wide Shot, Medium Close-Up, Macro Detail).
- Movement (Camera Vector): Specify physical motion (e.g., static lockoff, slow dolly-in, lateral tracking left-to-right).
- Duration: Allocate an exact target run-time (e.g., 2.5 seconds or 4.0 seconds).
- Required Assets: List input keyframes, face reference images, or product models required before generation.
Give Every Shot a Stable ID
Do not name your shots with casual labels like “the running shot.” When you revise a prompt or re-render a clip, unorganized naming causes file chaos.
Use a standardized naming formula that connects the slide to the shot: SlideID_ShotNumber_Revision. For example:
SC01_SH01_v01: Opening wide shot on Slide 1.SC02_SH01_v01: Medium tracking shot on Slide 2.SC02_SH02_v01: Close-up cutaway on Slide 2.
Attaching these stable IDs inside your speaker notes ensures that prompt engineers and video editors always know where each generated clip belongs.
Review the Sequence Before Generation
Reviewing your shot list inside a slide deck saves expensive generation credits before touching a video model.
Check Pacing, Coverage, and Missing Transitions
Walk through your shot list and evaluate overall coverage:
- Missing Eyelines: If Shot 1 shows an actor looking screen-right, does Shot 2 show the object of their attention on screen-left?
- Pacing Gaps: Sum up the durations across all shots. Does a 15-second spot accidentally total 22 seconds of planned footage?
- Action Gaps: Did you leave out a transition shot needed to get an actor from the kitchen to the car?
Catching these gaps inside the deck takes two minutes of editing. Catching them after generating high-resolution video takes hours of re-rendering.
Approve the Deck Before Producing Clips
Present the finished Claude Slides deck to your client or creative director. Once stakeholders sign off on the slide sequence and approve shot notes, freeze the pre-production deck. Treat the presentation as an immutable production agreement before generating visual assets.
Hand the Shot List to the Video Workflow
The final step is moving your approved shot specifications from the presentation into your production pipeline.
Export the Deck and Keep Slide IDs With Shot IDs
Claude Slides allows you to export your finished deck directly to PowerPoint (.pptx) or PDF.
Export the deck to preserve a permanent visual record of the approved pitch. When handing the shot specifications over to your technical team, export the speaker notes containing your shot IDs, camera movements, and prompt parameters into your production tracker.
Track Later Changes Outside the Presentation
Once video generation begins, do not use the slide deck to track daily render iterations. Presentations are visual planning frameworks, not database managers.
When managing complex campaigns where shot prompts, multi-model video clips, and audio tracks must stay aligned across a team, creators transfer their approved shot lists into dedicated production tools like the versatile CrePal workspace. Within
CrePal, creative teams organize scene cards directly from their approved shot IDs, pin character reference anchors, run generation passes across specialized video models, and assemble reviewable video drafts for post-production conforming.
Limits Creators Should Expect
While Claude Slides speeds up visual planning, creators must recognize clear practical boundaries:
Claude Slides Produces Presentations, Not Finished Storyboards
Claude Slides creates presentation slides with formatted text and clean container layouts. It does not natively sketch storyboard illustrations, render 3D camera angles, or export multi-panel drawing sheets. It organizes ideas into a sequential presentation structure, but human creators must supply visual reference assets.
Camera Logic and Video Continuity Still Need Human Review
An AI language model understands story beats, but it does not know the physical rules of filmmaking:
- No Lens Geometry: Claude cannot verify whether a 50mm lens transition will visually cut against an extreme wide angle without jump cuts.
- No Spatial 3D Awareness: The model cannot track physical character positions in a 3D environment across slides.
- No Video Rendering: Claude Slides is strictly a presentation tool; generating video files requires passing your finalized shot list to dedicated video generation engines.
FAQ
Which Claude plans currently include Claude Slides?
Claude Slides is part of the Artifacts feature set available on Claude.ai across Free, Pro, Team, and Enterprise plans. However, enterprise workspace administrators can toggle file creation and Artifact features on or off in Organization settings based on company data policies.
Can Claude Slides import an existing PowerPoint deck as a starting point?
No. Claude Slides cannot directly parse and visually reconstruct an uploaded .pptx presentation file inside the active Artifact canvas. However, you can upload existing presentation text outlines, slide scripts, or PDF exports into the chat context, and Claude can generate a fresh, editable slide deck based on that source material.
Does a PowerPoint export preserve speaker notes and slide comments?
Yes, exporting a deck to PowerPoint preserves text formatted within dedicated speaker notes sections. However, transient chat comments, on-canvas feedback highlights, and skipped slides are not embedded as native PowerPoint slide comments.
Can external collaborators edit or comment on a shared Claude Slides deck?
External viewers accessing a public shared Artifact link can view and present the deck, but they cannot edit or comment without an invited Claude account. On Team and Enterprise plans, real-time co-editing and comments are supported only among authenticated teammates who have been granted edit permissions.
Are connected-app sources embedded in a shared or exported deck?
No. When Claude references external data sources or connected-app tools during generation, the resulting slide deck contains only the final rendered text and layout artifacts. Live connections, underlying private workspace context, and external tool credentials are never packaged or exposed inside exported presentation files.
Conclusion
The fastest way to ruin an AI video project is jumping straight into prompt boxes without an approved visual plan.
Using Claude Slides as a storyboard framework bridges the gap between high-level client presentations and granular video execution.
By structuring your presentation with one narrative beat per slide, capturing technical camera parameters in speaker notes, and assigning stable shot IDs before generating footage, you eliminate guesswork, protect client alignment, and deliver cohesive multi-scene video on schedule.
