visuall.ai

If you're evaluating a video platform for a small business or marketing team, hosting and sharing are just the entry point. The features that actually determine whether a platform fits your workflow fall into four areas: privacy and playback control, collaboration and review tools, marketing and analytics capabilities, and practical limits like storage and mobile support. Most general-purpose tools (cloud storage, social networks, free hosts) cover hosting well but leave gaps in the other three. This guide walks through what each area means in practice, so you can map features to your own situation instead of comparing endless checklists.

Start by separating three jobs: hosting, editing, and marketing

Video platforms tend to bundle three distinct functions, and confusion usually comes from mixing them up:

• Hosting — storing a file, generating a player, delivering it reliably to viewers. This is the baseline.
• Editing — trimming, assembling, adding captions or branding. Some platforms include basic editors; others expect you to edit elsewhere and upload the result.
• Marketing and business features — privacy controls, lead capture, calls to action, analytics, team review workflows. These are what separate a "video host" from a "video platform."

A useful exercise: write down your last five video tasks (a product demo, a client pitch, a social clip, an internal training, a landing page embed). For each one, note which of the three jobs it required. If most of your tasks stop at hosting, a lighter tool may be enough. If several involve review cycles, gated access, or measuring viewer behavior, a fuller platform earns its cost.

Privacy and playback control: the business-vs-social divide

On social platforms, everything is public by default and wrapped in ads and recommendations. For business use, that's often the opposite of what you want. Look for:

• Granular privacy settings — can you restrict a video to specific people, a password, a domain, or an embed location? Can you make it unlisted but still embeddable?
• Ad-free playback — your product demo shouldn't end with a competitor's ad or an unrelated recommendation.
• Customizable embeds — control over player color, logo, and whether related videos appear. This matters when the video sits on your own site and represents your brand.
• Domain-level restrictions — the ability to limit playback to your own website prevents your content from being re-embedded elsewhere.

If your videos are purely promotional and public, these controls matter less. If you share client work, internal training, or pre-release material, they become the deciding factor.

Collaboration and review: the most common gap

This is where general-purpose tools most often fall short. A shared drive lets people comment on a file, but it doesn't give you a structured review process. A dedicated platform typically offers:

• Timestamped comments — feedback attached to a specific moment in the video, so "the logo looks off" points to an exact frame.
• Versioning — uploading a new cut while keeping the old one, so reviewers can see what changed.
• Approval status — a clear "approved" or "needs changes" state rather than a scattered email thread.
• Role-based access — reviewers who can comment but not download or reshare.

When this becomes relevant: as soon as more than two people need to sign off on a video, or when you're producing videos on a recurring schedule. For a solo operator publishing once a month, a simple comment thread may be sufficient.

Analytics and lead capture: beyond view counts

A raw view count tells you almost nothing actionable. Business-oriented platforms go further:

If your goal is brand awareness, basic view counts may be fine. If you're using video to generate leads or train staff, the deeper metrics are the reason to choose a platform over a free host.

Practical limits that affect daily use

Feature lists rarely mention the constraints that cause friction later. Check these before committing:

• Storage and bandwidth limits — how much you can upload, and whether high viewership triggers overage fees.
• Upload size and length caps — relevant if you work with long recordings or high-resolution footage.
• Mobile app support — can you upload, review, and respond to comments from a phone? For teams that shoot on mobile, this is a real workflow factor.
• Export and portability — can you download your originals and embed codes if you leave? Lock-in is a hidden cost.
• Integrations — does it connect to the tools you already use (your website builder, CRM, or project tracker)?

Deciding between a full platform and a lighter tool

Use these rough conditions as a starting point:

A lighter tool (free host, cloud storage, social platform) is likely enough if:

• You publish occasionally and mostly to public channels.
• One person handles video end to end.
• You don't need gated access or viewer-level analytics.

A dedicated platform is worth evaluating if:

• Multiple people review or approve videos.
• You need privacy controls, ad-free playback, or branded embeds.
• You're using video for lead generation, training, or client delivery.
• You publish frequently enough that manual workarounds cost more than a subscription.

Pricing and plan details change often, so check the platform's current plans page directly rather than relying on secondhand comparisons. The right approach is to list your actual requirements first, then match them against what each option offers — not the other way around.

Visuall turns a written idea into a finished video through a visible chain of steps on one canvas: you describe the film, the canvas agent splits it into scenes, you approve keyframes before anything is animated, then each approved frame is filmed with a model such as Veo 3.1, Seedance 2.0, or Gemini Omni. The practical payoff is that every step is a box you can see and change, and only the boxes you change get re-run — the rest is reused for free. This walkthrough covers the full path from an empty canvas to a stitched final video, plus where creators typically get stuck.

What the canvas actually is

Instead of a single prompt-to-video box, Visuall presents your project as a set of steps laid out on a canvas: your story, the AI scene plan, the keyframes, the model chosen for each shot, and the final stitch. The site describes it as "every video is a set of steps you can see and change."

That structure matters because it separates two things that are usually fused together in AI video tools: deciding what the shot looks like, and animating it. On the Visuall canvas those are different boxes, which is why you can approve a frame before spending anything on motion.

Step 1: Start from a template or describe the film

You have two entry points:

• Start from a template — the site shows examples like a product film, a vertical reel, a first-person powder run, and a short film set in Rome in 44 BC.
• Describe the film to the canvas agent — you write the story in plain language and the agent proposes the structure.

Either way, the output of this step is not video. It is a story box that the canvas will break down next.

Step 2: The story becomes a scene plan

The canvas agent splits your description into scenes with durations and shot descriptions. The site's skier example shows what this looks like:

Total: 10 seconds across 3 scenes. This is the box where you fix pacing problems cheaply — cutting a scene or rewriting a shot line here costs nothing compared to re-animating a clip.

Step 3: Generate and approve keyframes

Each scene gets a keyframe — a still image — before it becomes video. In the example, keyframes are generated with FLUX.2 at 16:9.

This is the approval gate. You look at the frame and decide: does this shot look right? If not, you change the prompt or the image and regenerate the keyframe. Only once you approve it does the frame move forward to animation.

For character consistency across scenes, the site's Rome example shows a related pattern: describe the character once in a paragraph, let the image model draw that face, then use an edit step to place the same face into each scene's frame. That keeps one character recognizable across four different locations.

Step 4: Animate the approved frames

Approved keyframes get filmed by a video model. The example uses Kling 3 at 5 seconds per shot, and the site names Veo 3.1, Seedance 2.0, and Gemini Omni as available models. Model choice is per shot, not per project — so you can use a cheaper or faster model for a simple wide shot and a stronger one for a hero shot.

If a scene needs dialogue or sound, Gemini Omni Flash is described as turning a frame into an 8-second clip that talks, with sound included.

Step 5: Re-run only what changed

This is the core mechanic and the reason the canvas is structured as boxes. When you change one shot, the other shots are not regenerated — they are reused. The site states it directly: "Change one shot, keep the rest," and "re-run only what changed; the rest is reused for free."

Practically, this means iterating on scene 2 does not cost you scenes 1 and 3 again. It also means the order of your work matters: lock the story and scene plan first, because changing the story re-runs the downstream boxes that depend on it.

Step 6: Stitch the final video

The last box joins the clips into one continuous video. In the Rome example, four clips become a single 32-second episode with the character's voice included. The whole project is summarized as 11 boxes, 225 credits, and about two minutes of waiting — a useful reference point for what a short narrative piece costs in steps and credits.

A worked example: the Rome episode

The site's behind-the-scenes breakdown is the clearest illustration of the full flow:

1. Describe her once — one paragraph about Mia; the image model draws the face she keeps in every shot.
2. One line per scene — four places in Rome, one per line; an edit step puts that same face into each frame.
3. Write what she says — each frame becomes an 8-second clip that talks, with sound.
4. Stitch the episode — the clips join into one 32-second video with her voice.

Notice that the character description and the scene list are separate inputs. That separation is what lets the same face appear in four different shots without re-describing her each time.

Where people get stuck

• Approving keyframes too fast. The approval gate is the cheapest place to fix a shot. A frame you dislike will not improve once animated.
• Editing the story after animating. Because downstream boxes depend on the story, late story edits re-run more than you expect. Lock the plan first.
• Treating model choice as global. Model selection is per shot on this canvas, so there is no reason to use one model for everything.
• Forgetting the reuse rule when budgeting. Re-runs are scoped to what changed, so cost scales with the number of boxes you touch, not the number of boxes in the project.

Getting started

The site offers a free start with 35 credits and states no credit card is required for that entry point. Current per-step costs are listed on the pricing page under "See what each step costs," which is the right place to check before committing to a multi-scene project, since credit use depends on how many scenes, keyframes, and animation runs you generate.

Visuall is built for two ends of the same spectrum: long-form campaign films and short vertical clips, both made on one canvas. According to the site, you can make a product film, a vertical Reel, a short film, or a feed-ready eight-second clip — and you approve every keyframe before it gets animated. If your workflow depends on reviewing stills before committing to motion, or on changing one shot without re-rendering the rest, this is the fit. If you need live-action footage or a fully automated one-click output, it is not.

The formats Visuall is designed around

The homepage frames the range directly: "AI video, from campaign film to viral clip. One canvas for the campaign film and the eight-second clip." The examples shown on the page cover:

• Product film — a horizontal, campaign-style piece
• Reel — vertical, "made for the feed"
• Reel — first-person action, e.g. "Fresh powder, first person," shot vertical
• Product film — built from three phone photos
• Short film — a narrative piece, e.g. "A day in Rome, 44 BC"

So both aspect ratios are in scope: vertical for social, horizontal for campaign and narrative work. The page does not list a fixed maximum length, so treat duration as something you set per project rather than a published limit.

The workflow that shapes what you can make

The canvas model is what determines the kinds of videos that are practical here. Every video is "a set of steps you can see and change": your story, the AI scene plan, and the model chosen for each shot. The key constraint-turned-advantage is stated plainly — "Approve the frames you like before they are animated, and re-run only what changed; the rest is reused for free."

That means the format best suited to Visuall is anything where you want shot-level control:

• Multi-scene narrative — a story broken into scenes, each with its own keyframe and animation
• Brand or product work — where a wrong frame is expensive and you want sign-off before motion
• Iterative social content — where you tweak one shot and keep the other seven

The page's own example walks through a 10-second, 3-scene skier sequence: an aerial dolly over a snowy ridge, a low tracking shot with powder spraying past the lens, and a wide shot of the skier carving into the valley. Each scene gets a keyframe (FLUX.2, 16:9), an approval step, then animation (Kling 3, 5s). That structure — story → scenes → keyframes → animate → stitch — is the template for anything you build.

A concrete example: the 44 BC Rome short film

The site's behind-the-scenes breakdown is the clearest illustration of what a finished Visuall video looks like. It describes "a vlog from Rome in 44 BC, by someone who doesn't exist," made in four steps across 11 boxes:

1. Describe her once — one paragraph about a character named Mia; FLUX.3 draws a consistent face used in every shot
2. One line per scene — four places in Rome, one per line; Edit Image places the same face in each
3. Write what she says — Gemini Omni Flash turns each frame into an 8-second clip that talks, with sound
4. Stitch the episode — Stitch joins the clips into one 32-second video with her voice included

The page notes this took 225 credits and "about two minutes of waiting." That gives you a realistic sense of scale: a 32-second narrative short with dialogue and sound, built from four scenes, is a normal-sized Visuall project.

What this means for your choice

Pick Visuall when your video needs scene-level approval and selective re-rendering — campaign films, product pieces, narrative shorts, and vertical social clips where you want to fix one shot rather than regenerate everything. The canvas, the per-shot model selection (Veo 3.1, Seedance 2.0, Gemini Omni, Kling 3, FLUX.2/FLUX.3 all appear on the page), and the "only what you change is made again" behavior are the reasons to choose it.

Look elsewhere if you need real captured footage, or if you want a single prompt to produce a finished video with no intermediate approval step — the whole design here assumes you want to inspect and approve frames along the way.

Visuall is a browser-based AI video and image generator built around a single canvas. Instead of writing one prompt and hoping for a finished clip, you describe a film, approve the still frames you like, and then animate each scene with a video model. It is aimed at creators who want shot-level control over AI video rather than a one-shot text-to-video box. You can start free with 35 credits and no credit card.

The core idea: approve the frame, then film it

Most AI video tools collapse everything into one generation step. Visuall splits it in two:

1. Keyframes first. A text-to-image model (the site shows FLUX.2 and FLUX.3 in its examples) renders still frames for each scene.
2. Animate second. Once you approve a frame, a video model turns it into motion.

The practical benefit is that you catch a bad composition while it is still a cheap image, not after you have paid for a video render. The site's own framing is "Approve the frame. Then film it."

Build it box by box

Visuall describes every video as a set of visible, editable steps on the canvas:

• Story — your description of the film.
• Scenes — the AI scene plan, broken into shots with durations (the example shows a 10-second film split into 3 scenes of 4s, 3s, and 3s).
• Keyframes — the approved stills, with model and aspect ratio noted.
• Animate — the video model applied per shot.
• Final video — the stitched output.

Because each step is a separate box, you can change one shot and keep the rest. The site states that only what you change is regenerated, and the rest is reused for free. That is the main structural difference from a single-prompt generator.

Models you can choose from

The site names several models across its examples and description:

Model availability and per-step costs are listed on the pricing page under "See what each step costs," so check there before committing credits to a long project.

A worked example from the site

Visuall's own behind-the-scenes demo is a 32-second "vlog from Rome in 44 BC" made by a person who does not exist. The described workflow:

1. Describe her once — one paragraph about a character named Mia; FLUX.3 draws a consistent face.
2. One line per scene — four locations in Rome, one per line; Edit Image places the same face in each.
3. Write what she says — Gemini Omni Flash turns each frame into an 8-second talking clip with sound.
4. Stitch the episode — Stitch joins the clips into one 32-second video with her voice.

That run used 11 boxes, 225 credits, and about two minutes of waiting. It is a useful reference point for scoping: a short multi-scene piece with dialogue is a few hundred credits, not a handful.

What it is good for

Based on the formats shown on the site, Visuall fits:

• Product films — including ones built from as few as three phone photos.
• Vertical social clips — short reels shot vertical for the feed.
• Short narrative films — multi-scene pieces with consistent characters and narration.
• Campaign work and quick viral clips — the site positions one canvas as handling both.

How to start

1. Go to visuall.ai and enter the canvas.
2. Start from a template or describe your film to the canvas agent.
3. Review the generated scene plan and keyframes; approve the frames you want.
4. Animate approved frames with your chosen video model.
5. Re-run only the shots you changed, then stitch the final video.

You begin with 35 free credits and no credit card required, which is enough to test the keyframe-then-animate loop on a short piece before deciding whether to buy more.

Visuall starts you with 35 credits and no credit card required, and credits are spent per step of the canvas workflow rather than per finished video. Because different steps and models can cost different amounts, the same length of video can consume very different totals depending on which models you pick and how many times you re-run a step. The site points to a per-step cost breakdown on its pricing page, so treat any single number as an example, not a fixed rate.

What the free 35 credits actually cover

The homepage states you can "Start free with 35 credits" and "No credit card." That is the whole of the free allowance as described — it is a one-time credit balance, not a stated monthly refresh, and the site does not describe it as a free tier that renews.

What 35 credits buys depends entirely on your step mix. To judge it, you need the per-step prices, which live on the pricing page under "See what each step costs." Without that table, the only concrete reference point the site gives is a much larger project:

That project used FLUX.3 for the character face, Edit Image to place the same face across scenes, Gemini Omni Flash to turn each frame into an 8-second talking clip with sound, and Stitch to join them into one 32-second video. So a 32-second finished video cost 225 credits across 11 steps — roughly 20 credits per step on average, though the site does not break down which step cost what.

At that average, 35 free credits would cover something in the range of one to two steps of a comparable project, or a much simpler single-shot test. That is an estimate built from one example, not a published rate.

Why credits are spent per step, not per video

The canvas is built as a chain of visible boxes: story → scene plan → keyframes → animation → stitch. Each box is a step you can see, edit, and re-run. Credits are consumed when a step runs.

The important consequence, and the one the site emphasizes most: "only what you change is made again" and "re-run only what changed; the rest is reused for free."

So if you approve keyframes, animate them, then decide one shot is wrong, you re-run that shot's step and the others are reused at no additional credit cost. This is the mechanism behind the site's claim that you can "Change one shot, keep the rest." It also means your credit total is driven by how many steps you execute and re-execute, not by final runtime alone.

Two practical implications:

• Iterating on keyframes before animating is cheaper than iterating after. Keyframe generation and animation are separate steps, so approving frames first (as the workflow encourages) avoids paying to re-animate shots you were going to reject anyway.
• Model choice affects cost. The site names several models across steps — FLUX.2 and FLUX.3 for keyframes, Kling 3, Veo 3.1, Seedance 2.0, and Gemini Omni for animation. Since the pricing page separates costs by step, different models within a step can carry different prices. Pick the model per shot rather than globally.

How to find your actual cost before committing

1. Open the pricing page and read the per-step cost section ("See what each step costs").
2. Map your intended project onto the canvas steps: how many scenes, which keyframe model, which animation model per shot, whether you need sound (Gemini Omni Flash generates talking clips with audio), and whether you need a final stitch.
3. Multiply steps by their listed costs. Compare that total against your 35 free credits to see how far the free allowance takes you.
4. Build the cheapest representative step first — one scene, one keyframe, one short animation — to confirm real consumption before scaling up.

Common sticking points

• Assuming 35 credits equals a finished video. The only published project example used 225 credits. A finished multi-scene video with sound is likely well beyond the free balance.
• Assuming a fixed per-second rate. The site gives no per-second pricing; cost is per step, and step costs vary by model.
• Assuming the free allowance renews. Nothing in the available material says it does.
• Re-running the whole chain after a small change. The reuse-for-free behavior only applies to steps you don't re-run, so scope your re-runs deliberately.

For exact current figures, the pricing page is the only authoritative source — the numbers above come from the homepage example and should be treated as illustrative.