Supports landscape, square, social, and vertical video assumptions.
PRODUCT PAGE
Frame-Aware Subtitle Rendering
Frame-aware subtitle rendering means the subtitle layout respects the shape of the video, the reading task, and the relationship between pinyin and Hanzi.
Sign in to uploadframe-aware subtitle rendering
OUTPUT PREVIEW
你吃饭了吗？
Have you eaten?
WHAT YOU GET
A focused path from speech to subtitle file.
Protects the visual relationship between pinyin and Hanzi.
Keeps English as a smaller meaning note rather than the main subtitle.
Makes ASS a precision layout format instead of a generic export option.
HOW IT WORKS
How this capability fits the SubChinese workflow.
- 01
Start from a Chinese video the user already has. The product begins with the source rather than assuming a useful platform caption track exists.
- 02
Create timed Chinese segments. Each sentence becomes an addressable unit that can be replayed, checked, corrected, and exported.
- 03
Connect the reading and meaning layers. Pinyin belongs to the Chinese characters, while English remains an optional interpretation layer.
- 04
Choose the output that matches the job. SRT carries portable timed language. ASS carries more deliberate learning layout.
SPECIFICATIONS
The capability in context.
| Layer | User-facing role | What it helps protect |
|---|---|---|
| Chinese source | The written record of speech | Accuracy and accountability |
| Pinyin | The reading path | Pronunciation-to-character connection |
| English | The meaning check | Comprehension without source replacement |
| Timing | The playback structure | A phrase’s place in the video |
| Export | The portable result | Reuse beyond the browser |
Why layout is part of understanding.
Subtitles are not displayed in an empty space. They share the frame with faces, movement, signs, interface elements, platform captions, and visual context. A language-learning subtitle has an even harder job because it may need to show Chinese, pinyin, and English without making the video unreadable.
Frame-aware rendering treats this as a product problem. The goal is not to decorate text. The goal is to make the relationship between layers easy to see while respecting the shape of the video. A vertical clip, a square social video, and a landscape lecture should not all receive the same reading surface.
This is where Pro value becomes visible. SRT can carry the language. ASS can carry the learning layout. That distinction gives paid users something more meaningful than just more processing minutes.
Why the capability matters in real content
Real Chinese videos are not arranged like beginner material. They contain names, unfinished sentences, cultural references, casual reductions, repeated phrases, and changes in speaking speed. A useful product has to support understanding without pretending that every line can be reduced to a perfect textbook example.
That is why SubChinese keeps the source, timing, reading support, and meaning support connected. The user can decide which layer deserves attention at a particular moment: listen first, read the Chinese, check pinyin, reveal English, or return to the same phrase later.
The result is a more respectful kind of assistance. It does not replace the content that made the video valuable. It gives the viewer a clearer way to approach it.
Why this is a product capability, not a marketing label
A capability should be visible in the user workflow. It should explain an action the user can take, a problem the user can avoid, or a result the user can keep. The SubChinese capability pages are designed around that standard: each concept appears in the preview, editor, playback, history, SRT export, or positioned ASS export.
This distinction also keeps the product language honest. We can describe a language layer, a reading relationship, or a frame-aware layout without claiming that automatic output is perfect. The value is in the structure that makes understanding and correction easier.
Why ASS deserves its own product story.
Many users see SRT and ASS as two file extensions. SubChinese should explain them as two promises. SRT is the safe file: simple, portable, inspectable, and accepted by many players. ASS is the precision file: it can preserve style and placement so pinyin can sit where it belongs.
The Pro story should focus on visual trust. If pinyin floats away from Hanzi, the user must do extra work. If pinyin remains visually attached, the subtitle teaches while it plays.
USE YOUR OWN VIDEO
Sign in to uploadStart from a file, not an existing subtitle track.
Sign in first, then upload a local video, review the generated transcript, keep English optional, and download a subtitle file.
WHEN THIS IS NOT WHAT YOU NEED
When this capability is not the right emphasis.
- If the user only needs a one-time summary, a full subtitle language layer may be more structure than necessary.
- If the source does not contain Chinese speech, the Chinese-focused workflow is not the right fit.
- If the destination player cannot support the chosen layout, the user should choose the more compatible output.
The product should make the useful layer available without forcing every viewer to display every layer at once.
QUESTIONS
Questions about frame-aware subtitle rendering.
Is this an implementation document?
No. It explains the user-facing product theory and capability. Internal infrastructure and provider details are intentionally not part of the public page.
Does automatic output still need review?
Yes. Names, context, homophones, segmentation, and translation nuance can require human judgement. The product makes review structured and reusable.
How do the capabilities connect?
They share the same timed language segments, so Chinese, pinyin, English, playback, editing, and export stay connected.