banuba.com

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.

Music video editing is not just a creative afterthought—it is a release strategy. The cut you publish, how long it runs, how it is paced, and which versions you distribute across platforms all influence how a song is promoted, how playlists and programmers treat it, and whether the video supports or complicates a chart run. For artists, managers, and labels, understanding the difference between creative editing and chart-rule compliance is essential before the first frame goes live.

Why the Edit Is a Business Decision

A song can exist without a video, but once a video is attached, it becomes part of the song's commercial identity. Editors and directors shape that identity through:

• Length – a full narrative video may run four to six minutes, while a platform-friendly cut may be trimmed to match the song's radio edit.
• Pacing – faster cuts suit short-form clips and social teasers; slower, sustained shots suit lyric videos and performance pieces.
• Versioning – the same song may need a clean version, an explicit version, a vertical cut, and a shortened edit for different outlets.

Each of these choices affects where the video can be placed, how it is promoted, and how it interacts with the song's chart eligibility.

The Main Edit Types and When to Use Them

Radio Edit

A shortened, often lyrically cleaned version timed to fit radio formatting. Use it when the song is being serviced to radio and you want the video to mirror what programmers are playing. If the video runs significantly longer than the radio edit, some promotional partners will use the shorter cut instead, which can split audience attention.

Lyric Video

A lower-cost, text-driven edit that can be released quickly, often before or alongside the official video. It is useful for maintaining momentum in the first days of a release, when fans want something to watch immediately. Lyric videos are also easier to update or replace if a lyric correction is needed.

Performance Cut

Focuses on the artist performing, often in a single setting or with minimal narrative. This is the most flexible format for promotional use because it can be trimmed, looped, or reformatted for vertical platforms without losing coherence.

Narrative Cut

A story-driven edit, usually the "official" video. It carries the most editorial weight but is also the hardest to shorten without losing meaning. If a narrative video is the primary release, plan a separate shorter cut for platforms that favor brevity.

Vertical / Short-Form Cut

A re-edited version framed for vertical screens, often using the hook or chorus. This is not simply a cropped version of the horizontal video—good vertical edits re-time cuts to the platform's pacing and place the most recognizable moment early.

How Edit Choices Interact With Promotion and Charts

Chart rules vary by territory and by chart, and they change over time. The safe approach is to treat the following as general principles rather than fixed rules:

• Version strategy matters. Releasing multiple edits of the same song can help promotion, but it can also complicate how streams and sales are counted if the versions are treated as separate releases. Check the current rules of the specific chart you care about before splitting a release.
• Timing matters. A video released before or at the same time as the song can concentrate attention. A video released weeks later can extend a song's promotional life but may miss the initial chart window.
• Platform fit matters. A video that is poorly formatted for a major platform will get less promotional support, which can indirectly affect the song's visibility.

None of this guarantees a chart position. Editing supports a release; it does not replace audience demand.

A Practical Version Plan

Before editing begins, decide which versions you actually need. A workable starting point:

1. Official video – the primary creative cut, full length.
2. Radio edit video – matches the radio edit length and lyrics.
3. Lyric video – fast turnaround, released early if needed.
4. Vertical cut – 15–60 seconds, hook-first, for short-form platforms.
5. Clean version – if the song has explicit content and you want broader placement.

For each version, note the intended platform, the target length, and the release date. This prevents last-minute re-edits that delay a rollout.

Common Mistakes to Avoid

• Assuming one cut works everywhere. A four-minute narrative video rarely performs well as a short-form clip without re-editing.
• Ignoring chart-rule details. If you plan to release multiple versions, confirm how they will be counted before release day.
• Letting the edit drift from the audio. If the video uses a different mix or edit than the released audio, make sure that is intentional and documented.
• Releasing the lyric video too late. Its main value is speed; if it arrives after the official video, it adds little.

What to Watch For in Industry Coverage

Industry news outlets track release strategies, version rollouts, and chart-rule changes. When reading coverage of a music video release, pay attention to:

• Whether the video is described as an official video, lyric video, or visualizer.
• Whether multiple versions were released and in what order.
• Whether the coverage mentions chart performance, and if so, which chart and which tracking period.

These details tell you more about the strategy than the video's creative style alone.

Bottom Line

Music video editing is a promotional tool with real consequences for how a song is positioned. Decide your version plan before you shoot, match each cut to its platform, and verify chart-rule details for your territory before splitting a release. Creative editing and release strategy are not opposites—the best rollouts treat them as the same job.

Banuba offers three distinct AR/AI products, and the right one depends on what your app needs to do. Face AR SDK adds real-time face tracking, beauty effects, and AR filters to live camera experiences like streaming and social apps. Video Editor SDK adds in-app video creation and editing, similar to a TikTok-style creator tool. Virtual Try-On (TINT) is a web-based try-on experience for e-commerce, covering makeup, eyewear, and jewelry. They can be used separately or combined, and all three are available as off-the-shelf modules rather than requiring you to build computer vision from scratch.

Face AR SDK: real-time effects for live camera use

This is the product to choose when your app's core experience is a live camera feed that needs to react to faces and hands in real time.

Key capabilities from Banuba's documentation:

• Real-time, on-device face tracking that follows up to 9 faces simultaneously
• Hand tracking and gesture recognition
• Beauty effects, virtual backgrounds, and color filters
• Live-streaming ready, with native integration for Agora, ZegoCloud, OpenTok, and WebRTC
• One SDK covering iOS, Android, Web, Unity, Flutter, and React Native

Best fit: live streaming apps, social platforms, and any product where users see AR effects applied to themselves or others in real time. If your users need to look at the camera and see filters or beauty effects instantly, this is the relevant product.

Video Editor SDK: in-app creation and editing

This product targets the editing workflow rather than the live camera. It's positioned as a way to build a "TikTok-class creator experience without writing an editor from scratch."

Core features include:

• Trimming, merging, drafts, and a timeline
• Picture-in-picture ("Duet") and AR video effects
• White-label output with your brand and no Banuba watermark
• One SDK for iOS, Android, Flutter, and React Native
• Quick integration, with agent skills available

Best fit: apps where users record or import clips and then edit them before sharing — social apps, creator tools, and platforms that want to keep video creation inside their own product instead of sending users to a third-party editor.

Virtual Try-On (TINT): web-based try-on for e-commerce

TINT is the commerce-focused product, and it works differently from the other two: it runs on the web rather than requiring an app install, and it's aimed at shoppers rather than creators.

What it covers:

• Skin-tone-accurate try-on for makeup, eyewear, jewelry, and accessories
• Personalized AI recommendations and seasonal color analysis
• Web-based and white-label, with no app install for shoppers
• Shopify and other e-commerce plugins, or custom integration
• New collection digitization in under 48 hours, and live in under 2 weeks per Banuba's claims

Best fit: e-commerce brands in beauty, eyewear, or jewelry that want shoppers to try products before buying. Banuba frames the value as more sales, higher lifetime value, and lower returns.

How to choose between them

A few practical notes on combining them:

• The three products solve different problems, so a single app could plausibly use more than one — for example, a social commerce app might use Face AR for live selling and TINT for product try-on.
• Platform support differs by product. Face AR covers the widest set (iOS, Android, Web, Unity, Flutter, React Native); Video Editor covers iOS, Android, Flutter, and React Native; TINT is web-based.
• Banuba lists a free trial across the products, so the most reliable way to judge fit is to test the specific SDK against your actual use case rather than comparing feature lists alone.

If you're still unsure, start from the user action you need to support: a live camera reaction points to Face AR, an editing workflow points to Video Editor, and a purchase decision on a product page points to TINT.

Banuba's platform support depends on which product you use. The Face AR SDK covers the widest range: iOS, Android, Web, Unity, Flutter, and React Native. The Video Editor SDK covers iOS, Android, Flutter, and React Native. Virtual Try-On (TINT) is a web-based product, so shoppers use it in a browser without installing an app. Windows and Mac support also appears in Banuba's documentation, but availability varies by product, so confirm the specific SDK before you commit.

Platform support by product

A dash means the source material does not list that platform for the product. It does not automatically mean the platform is unsupported — treat it as "not stated" and verify with Banuba if it matters to your build.

How to read this if you're choosing a stack

If you're building a native mobile app

Face AR SDK and Video Editor SDK both cover iOS and Android, so either fits a native build. Video Editor SDK is positioned for in-app video creation and editing — trimming, merging, drafts, timeline editing, picture-in-picture ("Duet"), and AR video effects — with white-label output and no Banuba watermark.

If you're building cross-platform

Flutter and React Native are supported by both Face AR SDK and Video Editor SDK, so a single cross-platform codebase can carry either product. Unity is listed for Face AR SDK only, which matters if you're targeting game engines or 3D-heavy experiences.

If you're building for the web

Face AR SDK lists Web support. Virtual Try-On (TINT) is web-based by design, aimed at e-commerce: skin-tone-accurate try-on for makeup, eyewear, jewelry, and accessories, with no app install required for shoppers. Banuba states new collection digitization can be completed in under 48 hours and a live try-on can be deployed in under two weeks.

If you need live streaming

Face AR SDK is described as live-streaming ready, with native integration for Agora, ZegoCloud, OpenTok, and WebRTC. If your app already runs on one of those stacks, that reduces the amount of custom work needed to add face tracking and AR effects to a stream.

What the SDKs actually do, briefly

• Face AR SDK — real-time, on-device face tracking (up to 9 faces), hand tracking and gesture recognition, beauty effects, virtual backgrounds, and color filters.
• Video Editor SDK — in-app video creation and editing, built so you don't write an editor from scratch.
• Virtual Try-On (TINT) — web-based try-on for e-commerce, with personalized AI recommendations and seasonal color analysis.

All three are off-the-shelf modules: they add augmented reality to an app or website without requiring you to build computer vision from scratch.

Before you integrate

1. Confirm the exact product-platform pairing. The table above reflects what Banuba lists; Windows and Mac support is described as product-dependent, so check the documentation for your specific SDK.
2. Check your streaming stack. If you need live AR, verify that your existing live-streaming provider is one of the supported integrations (Agora, ZegoCloud, OpenTok, WebRTC) or plan for custom work.
3. Decide app vs. browser. If your audience is shoppers on e-commerce, TINT's web-based model avoids an install step. If you need in-app creation tools, the Video Editor SDK is the relevant product.
4. Start with a trial. Banuba offers a free trial across its products, which is the practical way to verify that the SDK behaves as expected in your target framework before committing.

Banuba is a vendor of off-the-shelf AR and AI software development kits (SDKs) that add augmented reality features to apps and websites without building computer vision from scratch. It offers three main products — Face AR SDK, Video Editor SDK, and Virtual Try-On (TINT) — aimed at live streaming, social, and e-commerce use cases. If you need face filters, in-app video editing, or try-before-you-buy features and don't want to develop the underlying technology yourself, Banuba is a candidate worth evaluating.

The three core products

Face AR SDK

Real-time, on-device face tracking, beauty effects, and AR filters for live streaming, social, and try-on apps. Documented capabilities include:

• Face tracking that follows up to 9 faces in real time
• Hand tracking and gesture recognition
• Beauty effects, virtual backgrounds, and color filters
• Live-streaming integrations (native Agora, ZegoCloud, OpenTok, and WebRTC)
• One SDK for iOS, Android, Web, Unity, Flutter, and React Native

Video Editor SDK

In-app video creation and editing — positioned as a way to build a "TikTok-class creator experience" without writing an editor from scratch. Documented features:

• Core editing: trimming, merging, drafts, and timeline
• Picture-in-picture ("Duet") and AR video effects
• One SDK for iOS, Android, Flutter, and React Native
• White-label — your brand, no Banuba watermark

Virtual Try-On (TINT)

A web-based virtual try-on product for e-commerce, covering makeup, eyewear, jewelry, and accessories. Documented points:

• Skin-tone-accurate try-on
• Personalized AI recommendations and seasonal color analysis
• Web-based and white-label — no app install required for shoppers
• Shopify and other e-commerce plugins, or custom integration
• New collection digitization in under 48 hours
• Banuba claims live deployment in under 2 weeks

Platform support at a glance

Platform support varies by product, so confirm the specific combination you need before committing.

Who it's for

• Social and live-streaming apps that need face tracking, beauty effects, and AR filters.
• Creator and short-video apps that want built-in editing without developing an editor.
• E-commerce businesses in beauty, eyewear, jewelry, and accessories that want try-before-you-buy to reduce returns and lift conversion.

Banuba states its SDKs are "selected by hundreds of leading brands," though the page evidence does not name specific customers.

How to get started

The documented path is: pick the product matching your use case, request a free trial, and integrate via the SDK documentation. Banuba also mentions "Agent skills" as an integration aid for Face AR and Video Editor. The site references pricing and free trials but does not publish specific price figures in the available material — treat cost as something to confirm directly with Banuba.

What to verify before deciding

• Exact platform coverage for your target product, since it differs across the three SDKs.
• Pricing and licensing terms — not published in the source material.
• Try-on accuracy claims (skin-tone accuracy, 48-hour digitization, 2-week deployment) — these are vendor claims; validate against your own catalog and timeline.