Bilibili vs Youku vs Xigua — long-form destination order

Bilibili is Plan A for community and long-form fandom in Mainland China once YouTube-class embeds already fail. Youku China is Plan A for licensed catalog / Alibaba-ecosystem VOD. Xigua is Plan A for ByteDance long-form, not Douyin short-form. Pick one destination by job; keep the others residual. This Guide is that order — not another embed-fail remap.

What long-form video China destinations actually are

Hard names your destination order will use:

• Long-form video China — A destination people open for minutes-to-hours of VOD. Not an iframe hope, not a live room, not a Douyin short. Embed fail is the prior fork: YouTube alternatives in China. Live: livestream and Vimeo in China. In-product file: Wistia / Brightcove-class players.
• Bilibili — Community / long-form fandom as the destination. Creator-adjacent product films and community watch — not a surviving YouTube snippet. Product: bilibili.com. Creator rail: member.bilibili.com. Paid community buys sit on Bilibili ads China.
• Youku China — Alibaba-ecosystem licensed catalog / internet-TV VOD when that catalog job is already named. Product: youku.com.
• Xigua — ByteDance long-form VOD. Listed among China-market products on bytedance.com. Product: ixigua.com. Douyin short-form is a different rail: China consumer platform map.
• Residual, not a fourth Plan A — iQIYI when licensed long-form entertainment is already a named leftover. Tencent Video the same way. Do not staff them as Plan A in this order.
• Common myth — “Upload everywhere, then pick a winner from a traffic leaderboard.” Three destinations with no owner is not a Mainland China watch journey. One Plan A by job; the others capped.

Vocabulary first. Next: what must be true before Bilibili, Youku, or Xigua is real work.

What must be locked before Bilibili is Plan A

Missing a clear long-form job stops your product team before a “post the trailer to every China video brand” sprint is real work.

Precondition	Why your process stalls
Embed fail already decided — YouTube / Vimeo / Wistia-class hosts are not Plan A	A destination sprint is staffed while the site still ships a blocked iframe — or the reverse
Job locked — community / long-form fandom vs licensed catalog vs ByteDance long-form vs Douyin short vs live vs in-product file	Bilibili, Youku China, and Xigua are treated as synonyms; nobody owns Plan A
Destination vs player vs live named	An in-product MP4 sprint or a live-room sprint is billed as long-form VOD
Entity / creator rail on the chosen destination — Mandarin console, phone, partner or license path	Global brand accounts do not open Mainland China destinations by geo-toggle
Mainland China vantage proof on the destination the user opens, not only the marketing HTML host	Overseas QA “passes” while China users never find the watch
Supplementary cap if a second destination or a leftover global player stays	Unlimited “also post to Youku and Xigua” crowds out the Plan A cutover
Naming / trademark scoped before you spend on a destination brand	A China watch rail launches under a name you cannot hold — trademark in China

Product teams usually cannot treat “ship the same YouTube embed globally, plus a Bilibili backup” as the Mainland China plan. Naming one long-form destination is the floor.

From long-form job to Bilibili, Youku, or Xigua

Stage	Decision / outcome
1. Confirm the prior fork	YouTube / Vimeo / Wistia-class embeds are already out as primary. If that fork is still open, stop and use YouTube alternatives in China
2. Name the long-form job	Community / long-form fandom, licensed catalog, or ByteDance long-form? If the leftover is live or in-product file, leave this Guide
3. Pick one Plan A	Bilibili, Youku China, or Xigua by the job table below
4. Cap residuals	The other two destinations, plus iQIYI / Tencent Video if named, stay supplementary — not a second Plan A
5. Open entity / creator ops	Mandarin console, verification, content review where it applies
6. Prove from Mainland China	The destination URL / app the user actually opens (or China Network Diagnostics) — not only HQ upload success
7. Cut over, then re-test	China-facing trailers and help point at the named destination. Do not leave youtube.com or player.vimeo.com on that path

Hard gate — which destination is Plan A

Necessity: treating Bilibili, Youku China, and Xigua as interchangeable wastes the quarter — you underfund the rail that matches the watch job, or you staff three consoles and still have no Mainland China destination.

Job	Plan A	What must already be true
Community / long-form fandom (creator-adjacent product film, community watch)	Bilibili	Destination, not iframe; creator rail in motion (member.bilibili.com)
Licensed catalog / Alibaba-ecosystem VOD	Youku China	Catalog job named; Youku is the destination users open (youku.com)
ByteDance long-form (recommendation-driven medium-to-long VOD)	Xigua	Long-form job named; not Douyin short (ixigua.com)
Douyin / Kuaishou short-form	Not this Guide	China consumer platform map
Live room	Not this Guide	Livestream and Vimeo in China
In-product file on your site	Not this Guide	Enterprise video players — China-reachable file, not a destination swap
iQIYI / Tencent Video leftover	Residual only	Named catalog leftover; not a fourth Plan A (iqiyi.com)

Do not treat those destinations as drop-in iframe swaps. They are watch surfaces with their own creator, entity, and Mandarin ops rails.

Why mixing jobs stalls the destination

Engineering and ops constraints you must design around:

Constraint	What breaks	What to do
Prior fork not closed	A Bilibili / Youku / Xigua program runs while the China site still embeds YouTube or Vimeo. HTML 200, blank player.	Finish YouTube alternatives in China first. This Guide does not resurrect youtube.com.
Short-form treated as long-form	Douyin is staffed as the VOD destination. The long take never has a home.	Keep Douyin on the consumer-platform rail. Xigua is the ByteDance long-form row.
Live mixed into VOD	A live-room sprint is billed as long-form catalog.	Split live to livestream and Vimeo in China.
In-product player mixed into destination	Wistia / Brightcove is “replaced” by a Bilibili link inside a player chassis that still calls overseas hosts — or the reverse.	Destination or China-reachable file. Not both as the same ticket.
Three Plan As	Ops opens Bilibili, Youku, and Xigua with no owner. Nothing ships as the China watch path.	One Plan A by job. Cap the rest.
Ads rail treated as destination	A Bilibili ads account is reported as “video in China working.”	Ads is Bilibili ads China. This Guide is where people watch.

HQ upload OK → false confidence. A creator in Singapore can publish while ordinary Mainland China users never land on that destination.

Reporting residual Youku or Xigua traffic as the China watch path → wrong stack. A second destination without a cap is not Plan A.

Trademark ignored → spend on a name you cannot hold. Destination ops and trademark in China are sequential gates when the brand on the cover is the product.

What stalls teams that skip the destination order

• Geo-toggle thinking — Product treats “China video” as a YouTube region expand, then pastes the same file to Bilibili, Youku, and Xigua without a job.
• Embed-fail remap again — This article is opened as a second YouTube-alternatives fork. The order never starts.
• Douyin-as-YouTube — Short-form is treated as the long-form destination.
• Youku China as “the YouTube of China” — Licensed catalog is staffed for a community fandom job, or Bilibili is staffed for a catalog job.
• Xigua confused with Douyin — ByteDance long-form and ByteDance short-form are one ticket.
• iQIYI as a required fourth — Residual licensed entertainment is opened as Plan A.
• HQ laptop QA — Testers outside Mainland China never open the destination the user will open.
• No Mandarin / entity owner — Creator verification, review, and settlement sit on rails most global teams lack.
• Plugin defaults that re-inject YouTube — CMS video blocks restore youtube.com after the destination was named.
• Every-platform cutover with no sequence — Ops load explodes; the critical-path trailer stays on a blocked embed.

What “fixed” means: Mainland China users can start the long-form journeys you claim, on one named destination (Bilibili, Youku China, or Xigua); YouTube / Vimeo / Wistia-class hosts are gone from that path; live and in-product file leftovers are on their sibling Guides; residual destinations are named and capped. Overseas-only YouTube with a China storefront claim is not fixed.

China landing partner when the destination is the product

Most product teams exploring Mainland China entry need a China landing partner once they stop treating YouTube as Plan A — to open and operate the chosen long-form destination (Bilibili, Youku China, or Xigua), clear entity or creator verification, Mandarin console ops, content review where it applies, Mainland China proof, and the cutover so trailers and explainers actually play on that surface. Your team still owns which watch job is Plan A and which residual line to keep; the partner path makes that remapped China destination executable when those rails are not already in-house. Keeping a capped Youku or Xigua line beside a Bilibili Plan A does not remove the need for that China landing partner on the primary watch path.

What we can offer?

Long-form video China work for Mainland China is a which-destination order after YouTube-class embeds already fail. Chinaready helps your product team pick Plan A among Bilibili, Youku China, and Xigua — and make that rail executable:

1. China Readiness Assessment — Decide which long-form job is Plan A, whether Bilibili, Youku China, or Xigua owns it, and which entity, creator, and proof gates sit on the critical path before a cutover date.
2. China Access Acceleration — Keep China-facing pages and conversion paths reachable from Mainland China vantage so remapped destination links do not die on offshore-only HTML while the watch still fails.
3. China Product Hosting — Place China-critical pages (and any leftover self-hosted file) where ICP adjacency, entity consistency, and the named destination stay coherent after YouTube client hosts leave the journey.
4. Mobile App Distribution — Align China app builds with the destination or in-app path you actually claim — not mistake a YouTube SDK on a global binary for a Bilibili / Youku / Xigua plan.

Contact us when you need a Mainland China long-form destination order before you staff another “post to every China video brand” sprint.