The international micro drama landscape is dominated by a different set of players and platforms that originated from Chinese technology companies and have expanded globally. ReelShort, DramaBox, ShortMax, FlexTV, GoodShort, and TopShort collectively serve hundreds of millions of users across 200-plus countries.
For dubbing studios serving these international platforms, particularly studios in India that provide Hindi, Tamil, Telugu, and other Indian language dubs for content distributed through these global apps, understanding each platform’s specific technical requirements is essential for avoiding delivery rejections and building reliable vendor relationships.
This guide provides a technical comparison of dubbing specifications across the major international micro drama platforms, based on our production experience with each.
Why International Platform Specs Deserve Their Own Guide
Indian micro drama platforms (KukuTV, QuickTV, FlickTV) operate relatively straightforward content pipelines with accessible operations teams. If you have a specification question, you can typically get a direct answer from a content manager.
International platforms operate differently. Their content ingestion systems are more automated, their QC processes more formalized, and their rejection protocols more rigid. A delivery that fails automated technical validation may be rejected without human review and without detailed feedback. Understanding and meeting specifications precisely, before delivery, not after rejection, is critical.
Additionally, international platforms often change specifications as they scale. A spec that was accurate three months ago may have been updated. Studios serving these platforms must maintain active specification tracking and update their delivery templates accordingly.
ReelShort: The Quality Benchmark
ReelShort, operated by Crazy Maple Studio, is among the most commercially successful micro drama platforms globally. With tens of millions of monthly active users primarily in the United States, ReelShort has established itself as the quality benchmark for international micro drama distribution. Indian dubbing studios encounter ReelShort when the platform needs content localized for Indian audiences (Hindi, Tamil, Telugu) or when Indian-produced content is being distributed internationally.
Dubbing Quality Standard
ReelShort has the most rigorous quality expectations among international micro drama platforms. They require full lip-sync dubbing for all localized content with no exceptions. Beyond technical sync accuracy, ReelShort evaluates emotional performance quality, their QC team assesses whether the dubbed cliffhanger endings are as compelling as the originals. A technically perfect dub that sounds emotionally flat can be rejected on performance grounds.
This performance evaluation distinguishes ReelShort from platforms that only check technical compliance. Studios must invest in strong dubbing direction, not just accurate timing.
Technical Specifications
Audio delivery format:
- Stems: WAV, 48 kHz, 24-bit
- Final delivery: AAC 320 kbps (for platform ingestion)
- Both stems and final mix required
Channel configuration:
- Separate stereo dialogue track
- Separate stereo M&E track
- Final mixed stereo file (dialogue plus M&E)
Loudness:
- Integrated: -24 LUFS (±1 LU tolerance)
- True peak: -2 dBTP maximum
- Dialog-gating loudness measured per ITU-R BS.1770-4
Sync tolerance:
- Maximum 100ms drift on any individual line
- Zero accumulated drift at episode boundaries
- Bilabial consonant matching required on close-up shots
Subtitle delivery:
- Format: SRT
- Maximum 2 lines per frame
- Maximum 42 characters per line (including spaces)
- Forced narrative subtitles required for all on-screen text (signs, phone screens, written documents, text messages)
- Timing must match dubbed audio, not original audio
File naming convention: [SeriesCode]_EP[XX]_[ISO639-1_LangCode]_DUB_[STEM/MIX].[ext] Example: RS2847_EP05_hi_DUB_DLG.wav (Hindi dialogue stem) Example: RS2847_EP05_hi_DUB_MIX.aac (Hindi final mix)
Metadata:
- JSON metadata file per episode (character names, voice cast, adaptation notes)
- Series-level metadata document (character voice guide, adaptation approach summary)
Delivery method:
- Cloud upload through ReelShort’s partner content portal
- Automated technical validation runs on upload (loudness, format, naming, duration)
- Files that fail automated validation are rejected before human review
QC Process
ReelShort samples three to five episodes from each delivered batch for human review. Their QC team evaluates sync accuracy (frame-level assessment), emotional performance quality (subjective evaluation with standardized criteria), adaptation naturalness (does the dialogue sound native or translated?), technical audio quality (noise floor, artifacts, level consistency), and cliffhanger impact (does the last line make you want to see the next episode?).
A single sample failure triggers a full batch hold, no episodes from the batch are published until the issues are resolved, and the entire batch is re-evaluated. ReelShort provides detailed rejection reports with timestamps and specific observations, which is helpful for targeted fixes, but means the stakes per batch are high.
What Studios Need to Know
ReelShort is the most demanding platform to work with, but also the most rewarding. Accepted deliveries build a reputation that leads to ongoing volume. Rejected deliveries, particularly on performance grounds, can damage the vendor relationship. Invest extra in dubbing direction and QC for ReelShort deliverables.
DramaBox: The Revenue Leader
DramaBox, operated by Stary Group, is one of the most commercially successful micro drama platforms globally, reporting $323 million in revenue and $10 million in net profit in 2024. With over 90 million registered users across 200-plus countries, DramaBox operates at a scale that few competitors match.
Dubbing Quality Standard
DramaBox uses a tiered quality approach. Tier 1 markets (United States, United Kingdom, India, Brazil, Indonesia) require premium lip-sync dubbing. Tier 2 markets (smaller Southeast Asian and European markets) accept time-sync voice-over. This tiered approach allows DramaBox to allocate dubbing budget proportionally to market revenue potential.
For Indian languages (Hindi, Tamil, Telugu), DramaBox requires Tier 1 lip-sync quality, India is one of their priority growth markets.
Technical Specifications
Audio delivery format:
- Option A: AAC 320 kbps embedded in MP4 container
- Option B: Separate WAV stems at 48 kHz, 24-bit
- DramaBox accepts both, confirm preferred delivery method per project
Channel configuration:
- Stereo mixed (dialogue plus M&E combined) for Option A
- Separate dialogue and M&E stems for Option B
Loudness:
- Integrated: -23 LUFS (±1 LU tolerance)
- True peak: -1.5 dBTP maximum
- Note: DramaBox targets -23 LUFS, slightly louder than ReelShort’s -24 LUFS. A mix mastered for ReelShort at -24 LUFS will need loudness adjustment for DramaBox delivery, or you can master to -23.5 LUFS which falls within both platforms’ tolerance ranges.
Sync tolerance:
- Maximum 120ms drift (slightly more lenient than ReelShort’s 100ms)
- Lip-sync matching required for Tier 1 markets
- Time-sync alignment sufficient for Tier 2 markets
Subtitle delivery:
- Format: VTT (WebVTT) – note this differs from ReelShort’s SRT requirement
- Limited styling support (bold, italic for emphasis)
- Character limits vary by language per DramaBox’s guidelines document – CJK languages have lower character-per-line limits than Latin-script languages
- Forced narrative subtitles required for on-screen text
File naming convention:
- Platform-generated codes assigned at content registration
- Studios receive naming templates per project during onboarding
- Naming format varies by content batch, always use the template provided for each specific project
Metadata:
- Spreadsheet-based metadata (typically Excel or CSV)
- Episode-level: title, synopsis, character list, voice cast
- Series-level: genre, target audience, content advisory notes
Delivery method:
- API-based ingestion through DramaBox’s content management system
- Studios receive API credentials during vendor onboarding
- Automated technical QC runs post-upload and returns a compliance report within 30 minutes
- Failed uploads identify specific non-compliance points
QC Process
DramaBox provides a detailed quality scorecard for each delivery, rating on five dimensions:
| Dimension | Scale | Minimum Passing |
| Sync accuracy | 1–5 | 3.0 |
| Emotional performance | 1–5 | 3.0 |
| Adaptation naturalness | 1–5 | 3.0 |
| Technical audio quality | 1–5 | 3.0 |
| Delivery compliance | Pass/Fail | Pass |
The platform requires a minimum average score of 3.5 across the four scored dimensions. Scores below 3.0 on any single dimension trigger rejection. This scorecard approach is more structured than ReelShort’s subjective evaluation and gives studios clear benchmarks to target.
DramaBox also provides comparative feedback, if your delivery scores lower than other vendors dubbing the same content into different languages, they will flag the relative underperformance. This creates indirect competitive pressure that motivates quality.
What Studios Need to Know
DramaBox’s API-based delivery is more technically demanding to set up than simple cloud upload, but once configured, it is faster and more reliable. Invest time in proper API integration during vendor onboarding. DramaBox’s scorecard system provides excellent feedback, use it to calibrate your quality processes over time.
ShortMax, FlexTV, GoodShort, TopShort: The Emerging Platforms
Several newer international micro drama platforms are growing rapidly, often backed by Chinese technology companies expanding their micro drama infrastructure globally. These platforms include ShortMax, FlexTV, GoodShort, TopShort, MiniMax, and others that launch frequently.
Common Characteristics
These platforms generally share several traits. They operate coin-based or subscription monetization models similar to ReelShort and DramaBox. They source content primarily from Chinese production houses with some original international production. Their technology infrastructure is functional but less mature than ReelShort or DramaBox. Their dubbing specifications may be less formalized, sometimes provided verbally or through incomplete documentation.
General Specification Patterns
Based on our production experience with multiple emerging platforms, the following patterns apply to most:
Audio: MP4 with embedded AAC audio (256 kbps or higher). Some accept separate WAV stems. Confirm per-platform.
Loudness: Between -22 and -26 LUFS – wider variance than established platforms. Always confirm the specific target.
Subtitles: SRT is most commonly accepted. VTT accepted by some. Character and line limits vary.
Sync: Lip-sync expected for Hindi and major languages. Time-sync acceptable for smaller markets on some platforms.
File naming: Platform-specific. Always request the naming template in writing before starting work.
Delivery: Cloud upload (Google Drive, WeTransfer, or platform-specific portal). API-based ingestion is rare for newer platforms.
QC: Varies from no formal QC process (the studio’s QC is the only QC) to basic automated checks. Fewer platforms at this tier provide detailed quality feedback.
Working with Emerging Platforms: Best Practices
Request written specifications before starting. If the platform cannot provide a formal spec document, request sample approved deliveries from other vendors. Reverse-engineer the specifications from these samples.
Deliver a three-episode technical sample before committing to batch production. This catches spec mismatches before they affect 50-plus episodes. The cost of three test episodes is trivial compared to the cost of re-delivering an entire batch.
Over-deliver on technical quality. When specifications are ambiguous, deliver at the highest reasonable quality, higher bitrate, stricter loudness compliance, and more precise sync. It is always easier to down-convert quality than to upgrade rejected deliverables.
Document everything. Record all specification discussions in writing (email confirmations, not just chat messages). When specs change mid-project, document the change with dates and confirmation from the platform contact. This protects you if delivery disputes arise.
Build relationships, not just transactions. Emerging platforms are growing rapidly. A studio that establishes itself as a reliable vendor during the platform’s early growth phase becomes the preferred partner as the platform scales. Early reliability is rewarded with increasing volume and better commercial terms.
Cross-Platform Delivery Optimization
Studios serving multiple international platforms can optimize their workflow through a single-master, multi-export approach.
The Single Master Workflow
Record at the highest common quality standard. WAV 48 kHz, 24-bit is universally accepted. Never record at lower quality than any platform requires.
Create separate stems for every project. Even if a platform only requires mixed delivery, maintaining separate dialogue and M&E stems allows you to serve any platform from the same source material. This is especially important when the same content is distributed through multiple platforms, a Chinese series might appear on both DramaBox and ShortMax in different territories.
Master to the strictest loudness target. If your platforms target -23 LUFS and -24 LUFS respectively, master your dialogue stems to sit within both tolerance ranges. A mix at -23.5 LUFS with ±1 LU tolerance passes both -23 (DramaBox) and -24 (ReelShort) specifications.
Build platform-specific export templates. In your DAW, create export presets for each platform covering format (WAV, AAC, codec settings), loudness target, channel configuration, and sample rate or bit depth conversion. Run each export from the same master session. This eliminates the need to remix for each platform.
Automate file naming. A simple script or batch renaming tool that converts your internal file names to each platform’s naming convention saves hours on large batch deliveries and eliminates the manual naming errors that cause automated ingestion rejections.
Specification Tracking
Maintain a living document – spreadsheet or database – that tracks current specifications for every platform you serve. Include columns for audio format, loudness target, sync tolerance, subtitle format, naming convention, delivery method, and the date each spec was last confirmed.
Assign one team member to verify specifications with each platform quarterly. When a spec changes, update the export templates immediately before the next delivery.
Sukudo Studios maintains current technical specifications for all major international micro drama platforms and updates delivery templates as specifications evolve. Our cross-platform delivery optimization ensures you receive publish-ready files for ReelShort, DramaBox, and any other platform from a single production pipeline. Start your international platform dubbing project.
Frequently Asked Questions
No. ReelShort and DramaBox Tier 1 markets require lip-sync. DramaBox Tier 2 markets and some emerging platforms accept time-sync voice-over. Always confirm per-title and per-market requirements, some platforms designate the dubbing quality tier in their content briefs.
Loudness non-compliance is the single most frequent automated rejection trigger. Different platforms target different LUFS values, and a mix that passes one platform’s specification may fail another’s. Always measure loudness before delivery and verify against the specific platform’s target.
If two platforms have compatible specifications, same audio format, same loudness target, same channel configuration, the same audio file can be submitted to both. However, subtitle formats (SRT vs VTT), file naming conventions, and metadata requirements almost always differ and must be customized per platform.
ReelShort has the most rigorous QC process and the highest emotional performance expectations. However, they also provide the most detailed feedback when issues arise, which makes improvement straightforward. Emerging platforms can be harder in a different way, ambiguous specifications, inconsistent QC, and limited feedback make it difficult to know what standard you are targeting.
Most platforms accept vendor applications through their business or content partnership pages. Prepare a showreel demonstrating lip-sync dubbing quality across genres, documentation of your studio capabilities and security certifications (TPN Blue Shield is a significant advantage), and references from existing platform clients. A pilot project (3 to 5 episodes) is typically required before full batch approval.
