Bilibili Subtitles: CC vs Burned-In
Bilibili subtitles come in two forms: platform-hosted CC tracks, and subtitles burned into the picture. The first can be searched and toggled by viewers; the second nobody can turn off, but the platform can't read the text. Decide what the video needs before uploading, or you'll discover you lost search or lost presentation after the fact.
Two forms, told apart
CC subtitles (platform-hosted): you upload a subtitle file and the platform hosts it as a toggleable track. Viewers switch it on and off; the platform uses the text for search, translation and accessibility. Burned-in subtitles: rendered into the picture as pixels — survive forwards and screenshots, but the platform sees only pictures and can't read a word.
The core difference is "can the platform read your text" — it decides whether search, recommendations and auto-translation can use your copy. A video without a subtitle file still gets auto-captions from audio, but that track belongs to the platform and its mistakes are unfixable.
What CC suits
Long videos, tutorials, commentary — viewers toggle or cross-check lines. Content you want found in site search — subtitle text enters the index, every line becomes retrievable. Multilingual audiences — the platform can auto-translate from the text track; especially useful for tutorials where viewers follow terminology line by line.
Upload as SRT or VTT; the platform converts. Run the subtitle checker before submitting to catch oversized or over-speed cues.
What burned-in suits
Remixes, memes, short clips — text survives forwards and screenshots. Emphasis that must not be turned off — key conclusions stay on screen. Players without a subtitle toggle — burned text is player-independent, what you see is what you get.
The cost: one changed word means re-exporting the cut, and the platform can't read the text. Multilingual hard subtitles need one cut per language, so cost grows with language count — another reason to build a master first and derive from it.
When you need both
Same content, searchable and stable to present: give both. CC goes to the platform for search and toggling; the burned cut covers forwards, embeds and remixes where text must travel.
Workflow: keep the SRT as master, produce a platform track with the SRT to VTT tool, then burn a final cut with the burn tool. The complete comparison: burned-in vs soft subtitles.
Check before uploading
Cue count complete and timeline not shifted overall (shifts slide with the subtitle shift tool); line length within bounds — Chinese max 18 per line, Latin max 42 with 2 lines; reading speed — Chinese under 9 chars/second, Latin under 20; each cue holding 1–7 seconds. Pass these and neither presentation nor search will stumble.
A few reminders: CC and burned aren't exclusive — important content usually gets both; slide whole-timeline shifts with a tool rather than editing cue by cue; for long videos with many chapters, run the checker before submitting — cheaper than being called out after publishing. Set the burned version's font and position once at burn time to avoid repeated exports; for multilingual content, finalize the master timeline first, then translate per language without re-timing.
FAQ
How do I upload CC subtitles on Bilibili?
Upload the subtitle file (SRT or VTT commonly) in the manuscript manager; the platform hosts it as a toggleable track. Run the subtitle checker first for safety.
Can CC and burned subtitles coexist?
Yes, and often should: CC for search and toggling, burned for text that travels with forwards and screenshots. One SRT master, two exports.
Do burned subtitles hurt searchability?
Burned text is pixels the platform can't read by default, so part of the searchable signal is lost. If search matters, submit the subtitle file too; the platform also auto-generates captions from audio, but you can't fix its errors. Details: burned-in vs soft subtitles.