What you will prepare
This is not a click-by-click walkthrough of the VMAI Showcase publish button. It is a pre-publish checklist for a completed AI video. Use it to decide whether the video is ready for public viewing and to avoid missing title, description, tags, subtitles, format, and rights checks at the last minute.
By the end, you will have:
- the version you want to publish and the audience it serves;
- a rights and sensitivity check for images, music, voices, and subtitles;
- a draft title, description, tags, and video language;
- a rule for showing or hiding subtitles by default;
- an MP4 (H.264) and plan-limit check;
- a post-publish edit or unpublish threshold.
Step 1: Name the role of the version
Start by naming the file you want to publish. The question is not “Which file is newest?” It is “What job does this version do?”
| Version name | Meaning | Publish decision |
|---|---|---|
| Review version | Used internally to inspect the flow | Do not publish, or share only in a limited context. |
| Revision version | Fixes one known problem | Compare it against the target issue. |
| Publish candidate | Safe and useful for outside viewers | Check title, rights, subtitles, and format. |
| Hold version | Looks good but has uncertain rights or data | Do not publish yet. |
A publish candidate should be more than “safe enough.” You should be able to explain why this video should be seen.
Step 2: Check rights and sensitivity first
The first publish check is not video quality. It is safety. Even if you created the video, the materials inside it may come from different sources.
Fill this table before writing the public metadata.
| Area | Question | Result |
|---|---|---|
| Images and video | Are customer names, account labels, order IDs, internal URLs, or unreleased screens absent? | |
| Music and effects | Do you have the right to use the audio publicly? | |
| Voice | Is it your voice or a voice you have permission to use? | |
| Subtitles and script | Are private names, prices, terms, or internal phrases absent? | |
| Brand marker | Does this video need a logo or watermark? |
If any answer is uncertain, keep the video as a hold version. Stopping before publication is much easier than removing a link after it spreads.
Step 3: Write the title as a viewer promise, not an internal filename
The title in the VMAI Showcase publish form is required. In the current implementation, titles are validated between 2 and 100 characters. Short is fine, but outside viewers need to understand the point of the video.
A useful title usually includes one of three signals.
- Result: What does the video show?
- Audience: Who is it for?
- Use case: Where will it be used?
Examples:
| Internal title | Public title |
|---|---|
final_v3 | “One-minute product intro for a new feature” |
shorts_test | “Silent-friendly campaign announcement video” |
client_demo | “Service summary video for a sales meeting” |
A title that overpromises may earn a click, but it loses trust. Promise only what the video actually shows.
Step 4: Use the description to add context in one or two sentences
The description is optional, but it is useful for a public video. The publish API validates descriptions at 500 characters or less. Accuracy matters more than length.
Use this template.
textThis is a [duration/format] video for [audience] explaining [topic]. The key scenes are [main scenes], and [subtitle/voice/rights note] has been checked.
Example:
textThis is a 45-second intro video for new users explaining the service flow. It uses only public-safe product captures, with subtitles shown by default for silent viewing.
Do not put reviewer names, customer names, private contract terms, or non-public pricing in the description.
Step 5: Choose up to five tags with clear roles
The VMAI publish form handles up to five tags, with each tag in the 2–20 character range. More tags are not automatically better. Better tags explain what group the video belongs to.
Use this structure.
| Tag role | Examples | Purpose |
|---|---|---|
| Topic | product, education, event | Names the subject. |
| Format | shorts, tutorial, demo | Sets viewing expectations. |
| Status | public-preview, approved | Clarifies reuse or review state. |
| Campaign | summer-campaign, onboarding | Helps you find it later. |
Use tags in the language your intended viewer understands. English videos usually work better with English tags. Korean videos are often clearer with Korean tags. Mix languages only when there is a real reason.
Step 6: Decide language and subtitle visibility
The Showcase publish form includes video language and subtitle visibility. Language helps the Showcase context and filters. Subtitles may be shown by default, and viewers can toggle them.
Turn subtitles on by default when:
- many viewers may watch without sound;
- narration is important to understanding the video;
- caption length and placement have already been reviewed.
Recheck subtitles when:
- captions cover a product, face, or key screen area;
- numbers, names, or product terms may be wrong;
- long captions are difficult to read on mobile.
If subtitles are a core part of the final video, review Burn SRT/VTT Subtitles into a Video or Preview and Reuse Caption Styles with Subtitle Style Editor first.
Step 7: Confirm format and publishing limits
VMAI Showcase publishes from a completed video version, and the publish API checks MP4 (H.264) compatibility. Your plan can also limit how many videos you can keep published. Check these before you reach the publish moment.
- Is this a completed video version?
- Was the result rendered as MP4 (H.264)?
- Are you within the published-video limit for your plan?
- Has this same version already been published?
- Could the title, description, or tags fail content moderation?
If the format is wrong, revisit export settings before publishing. If you are unsure which export decision matters, start with Plan AI Video Render Settings Before Export.
Step 8: Define the post-publish edit rule
You can edit public metadata later, but a shared link creates an immediate first impression. Before publishing, decide what would make you edit or unpublish the video.
Edit when:
- the title does not describe the video accurately;
- the description contains stale or unclear information;
- tags or language do not match the actual content;
- subtitle visibility hurts the viewing experience.
Unpublish when:
- an image, audio track, or voice has unclear rights;
- customer data or internal information is visible;
- the video shows expired pricing, benefits, or policy details;
- a review-only version was published by mistake.
Copyable checklist
markdown# VMAI Showcase pre-publish checklist ## 1. Version - Publish candidate version: - Intended audience: - Publish purpose: ## 2. Rights and sensitivity - Images/video sources are public-safe: - Music/effects rights are clear: - Voice rights are clear: - Subtitles/script contain no sensitive data: - Brand/watermark needed: ## 3. Title and description - Title (2–100 characters): - Description (500 characters or less): - No exaggerated claim: ## 4. Tags and language - Tag 1: - Tag 2: - Tag 3: - Video language: ## 5. Subtitles - Subtitle visibility: on / off - First five seconds are readable: - Names, numbers, and product terms checked: ## 6. Format and limits - Completed video version: - MP4 (H.264): - Plan publishing limit checked: - Same version not already published: ## 7. After publishing - Conditions for editing metadata: - Conditions for unpublishing:
Next step
Once the checklist is filled, watch the completed video again as a publish candidate. If you are tempted to rebuild the whole video, narrow the next fix with Plan an AI Video Revision Pass. For the broader reason this pass matters, read Is Your AI Video Really Ready to Publish?.
Tutorial Complete!
You've read this tutorial. Move on to the next step.
Plan a Reusable Media Library for AI Video Projects
Prepare a Reference Pack for AI Video Generation
Found this tutorial helpful?
Subscribe to get notified when we publish new tutorials and guides. No spam, unsubscribe anytime.
Comments
Please login to leave a comment
LoginNo comments yet. Be the first to comment!