Is Seedance Open Source? What's Actually on GitHub & Hugging Face
Seedance is not available as open source, open weights, or a local install, and as of August 15, 2026 ByteDance has published no source repository, no licence and no weight download for any version of it. We checked twelve specific paths for one — five GitHub URLs, five Hugging Face URLs and two official ByteDance pages — plus the full public repository listings of both ByteDance Hugging Face organisations. Nothing.
That is the short answer, and it is worth separating from a much noisier claim floating around search results and AI answers: that Seedance can be “deployed locally from Hugging Face.” Hugging Face does host repositories named after Seedance. What those repositories contain is the interesting part, and it is not weights.
This page keeps three questions apart that most coverage collapses into one: whether the code is open source, whether the weights are public, and whether you can run it locally. They have different answers for different models, and conflating them is how the “Seedance is on Hugging Face” story got started. Every reading below was taken on 2026-08-15 (data checked 2026-08-15) and every check is one you can repeat yourself in about five minutes — the method is at the end.
Three questions, not one
“Open source” has become a marketing word, so here is the vocabulary this page uses, with a real example of each so the categories are not abstract.
| Term | What it actually means | Example on 2026-08-15 |
|---|---|---|
| Open source (code) | The training or inference source code is published under a recognised licence you can read, fork and redistribute | ByteDance’s own ByteDance-Seed/Bagel repository, described on GitHub as an “Open-source unified multimodal model” |
| Open weights | The trained model file itself is downloadable — but under whatever licence the publisher attaches, which may restrict commercial use | Wan-AI/Wan2.2-TI2V-5B-Diffusers, Apache-2.0, 195,127 downloads |
| Open weights, custom licence | Downloadable, but governed by a bespoke agreement rather than a standard open-source licence | MiniMaxAI/MiniMax-H3, licence field other, licence name minimax-h3-community-license-agreement, 1,997,541 downloads |
| Runnable locally | You can load the weights on hardware you control, with no vendor in the request path | Any of the above, given enough VRAM |
| API access | You send a prompt to someone else’s servers and pay per generation | Seedance, every version |
Seedance sits in the last row only. The distinction matters commercially: an Apache-2.0 checkpoint and a “community licence” checkpoint are both downloadable, and only one of them is unambiguously free to use in a commercial product. A model with no checkpoint at all — Seedance — sidesteps the licence question entirely, because your rights come from the platform’s terms of service rather than from a model licence.
Is the Seedance source code on GitHub?
No repository named Seedance exists under any ByteDance GitHub account we could find.
A GitHub search for repositories named seedance under the bytedance account returns zero results. Restricting a seedance search to the ByteDance-Seed organisation returns three repositories — Seed-Coder, Stable-DiffCoder and par-protein — none of which is Seedance; they match on the string “Seed”, which is the research team’s name. The organisation’s own bio reads: “Established in 2023, the ByteDance Seed team is dedicated to discovering new approaches to general intelligence and pushing the boundaries of AI.” Its pinned work on that date included Bagel, Depth-Anything-3, VeOmni, Seed1.5-VL and Triton-distributed. No video generation model among them.
Because “we couldn’t find it” is a weak claim on its own, here are the exact URLs we requested and the status each returned:
| URL checked | HTTP status on 2026-08-15 |
|---|---|
github.com/bytedance/Seedance | 404 |
github.com/bytedance/seedance | 404 |
github.com/ByteDance-Seed/Seedance | 404 |
github.com/ByteDance-Seed/Seedance-2.0 | 404 |
github.com/volcengine/Seedance | 404 |
huggingface.co/ByteDance/Seedance-2.0 | 401 |
huggingface.co/ByteDance-Seed/Seedance | 401 |
huggingface.co/ByteDance-Seed/Seedance-2.0 | 401 |
huggingface.co/ByteDance-Seed/Seedance-1.0 | 401 |
seed.bytedance.com/en/seedance | 200 |
seed.bytedance.com/en/seedance2_5 | 200 |
One caveat we will not paper over: Hugging Face returns 401, not 404, to an anonymous request for a repository that does not exist, because it cannot distinguish “missing” from “private or gated” without authenticating you. A 401 is therefore not proof of absence on its own. That is why the weight question below is settled with organisation listings and the search index rather than with status codes.
The two ByteDance pages that do return 200 are informative for what they omit. The Seedance product page on seed.bytedance.com carries the buttons “Try Now”, “Get API”, “Compare Now” and “Full Technical Report”. Across that page there is no sentence mentioning open source, weights, download, GitHub, Hugging Face or a licence. The most recent official Seedance announcement, the ByteDance Seed blog post dated July 31, 2026, describes access in a single sentence: “Today, Seedance 2.5 is rolling out on Jimeng AI, Doubao Pro, and other platforms, with API access coming soon via BytePlus ModelArk.” Apps and an API. No third option is offered.
Are the weights on Hugging Face? Yes and no — mostly no
This is where the confusion is manufactured, so it deserves the detail.
The official accounts hold no Seedance model. On August 15, 2026, ByteDance-Seed listed 59 public model repositories and ByteDance listed 57. We pulled both full listings through the Hugging Face API and searched them: none of the 116 repositories is a Seedance model. Not gated, not hidden behind an access request — absent.
Searching for “seedance” returns 13 repositories, none of them ByteDance’s. Here is what those 13 actually contain:
| Repository group | Count | Weight files | Downloads |
|---|---|---|---|
README-only repositories (.gitattributes + README.md) | 8 | 0 | 0 each |
| Repository with prompt templates and a config, no checkpoint | 1 | 0 | 0 |
Repository containing only a .gitattributes | 1 | 0 | 0 |
| LoRA adapter checkpoints from one user’s training run | 3 | 18 files each | 0 each |
Every one of the 13 showed zero downloads. For a model as widely searched as Seedance, that number alone tells you nobody is pulling weights from these repositories, because there are none to pull.
The README-only cluster is not accidental. Take RTX2o/Seedance-2-AI-Video-Generator, created June 8, 2026: two files, a 3,190-byte README and a .gitattributes, tagged text-to-video, image-to-video, multimodal, diffusion, dit, lip-sync, physics-simulation and license:other. It reads like a model card. Its “How to Use” section says the quiet part out loud:
“Due to the massive computational resources required to run the Dual-branch DiT architecture, the full Seedance 2.0 model is currently hosted exclusively on our official platform.”
followed by “You do not need to download heavy weights, configure environments, or rent expensive GPUs,” and a link to a third-party generator site — not a ByteDance domain. Semub/Seedance-2-AI-Video-Generator-free, created eleven days later, carries a README of exactly the same 3,190-byte length, the same .gitattributes length and the same seven tags: the same template, re-uploaded under a different account. These pages exist to rank in Hugging Face search and hand traffic to a clone site, a pattern we documented separately in our guide to the official Seedance site versus the clones.
The three exceptions are worth stating precisely rather than dismissing. One user’s repositories, named in the pattern afd_ar_seedance15_..., do contain real weight files — 18 each, including LoRA adapter files, a discriminator checkpoint and eight rank-sharded optimizer files under a checkpoint-step-60/ path. Two things follow. First, a LoRA adapter is a delta, not a model: it requires a base model to attach to, so it cannot substitute for weights that were never released. Second, we could not read those repositories’ adapter_config.json to see which base model they name — Hugging Face rate-limited our repeated requests on August 15, 2026 and returned no body — so we make no claim about what they adapt. What we can say is that they carry zero downloads and are not published by a ByteDance account.
Hugging Face Spaces tell the same story: a search for “seedance” returned 39 Spaces on August 15, 2026, and none of them runs under a ByteDance account. A Space is a hosted demo app, not a weight repository; a Space named “Seedance-Free” is somebody’s front end, and what it calls behind the scenes is a question about their API bill, not about model availability. That is the same structural point our free Seedance investigation reaches from the pricing side.
Can you run Seedance in ComfyUI?
You can add a Seedance node to a ComfyUI workflow. You cannot run Seedance on your own GPU. Both halves of that sentence are true, and the gap between them is exactly what “ComfyUI support” hides.
ComfyUI’s own source tree settles it. ComfyUI keeps two kinds of model nodes in two different directories. Nodes that load weights from your disk live in comfy_extras/ — that is where nodes_wan.py, nodes_hunyuan.py, nodes_mochi.py, nodes_cosmos.py and nodes_lumina2.py sit. Nodes that call a paid remote service live in comfy_api_nodes/, alongside nodes_openai.py, nodes_kling.py, nodes_veo2.py and nodes_runway.py.
On August 15, 2026 we read both directories on ComfyUI’s master branch. comfy_extras/ contained 135 items (132 files, 3 subdirectories) and not one mentioning Seedance or ByteDance. Seedance appears only in comfy_api_nodes/nodes_bytedance.py, where the code:
- defines a
SEEDANCE_MODELSmap of four API identifiers —dreamina-seedance-2-5-260628,dreamina-seedance-2-0-260128,dreamina-seedance-2-0-fast-260128anddreamina-seedance-2-0-mini; - sends its requests to endpoints under
/proxy/byteplus-seedance2/api/v3/contents/generations/tasksand/proxy/seedance/assets; - passes a hidden
api_key_comfy_orgcredential and attaches a price badge to the node; - lists
seedance-1-0-lite-t2v-250428andseedance-1-0-lite-i2v-250428underDEPRECATED_MODELS.
A node with a price badge and a proxy endpoint is a shop front, not a runtime. Note also that those four identifiers were read from ComfyUI’s source, not from ByteDance’s own catalogue; on August 8, 2026 no Seedance 2.5 model ID rendered in BytePlus’s public model list, as recorded in our Seedance access guide.
The community node packs agree, unanimously. The ComfyUI-Manager registry — the list ComfyUI Manager reads when you browse custom nodes — held 5,883 node packs on August 15, 2026. Eight mention Seedance. All eight describe themselves as API wrappers:
| Node pack | What its own description says it calls |
|---|---|
seedance2-comfyui-byteplus | “BytePlus ModelArk Seedance 2.0 direct API generation” |
ComfyUI-Seedance2-Direct-BytePlus | “calling Seedance 2.0 through a direct BytePlus ModelArk API key” |
ComfyUI-Volcengine-Seedance | “Volcengine Ark Seedance video generation tasks” |
comfyui-seedance-nodes | “BytePlus / ByteDance Seedance 2 video-generation API” |
ComfyUI-Seedance2-AllRef | “generating videos using ByteDance Seedance 2.0 API” |
seedance2-sjinn-comfyui | “Seedance 2.0 video generation in ComfyUI via Sjinn.ai API” |
comfyui-sunra | “Sunra.ai’s FLUX.1 Kontext and Seedance models” |
ComfyUI-Higgsfield-Direct | “Direct Higgsfield API integration… Use your own API key” |
Eight out of eight. Not one advertises a checkpoint, a model folder, or a VRAM requirement — the three things a local video model node cannot avoid mentioning. A separate GitHub project, Anil-matcha/seedance2-comfyui, is explicit in its README that generation runs through api.muapi.ai endpoints and that an account there is required; its Python dependencies are requests, Pillow, numpy, torch and opencv-python, which is the dependency list of an HTTP client that handles images, not of an inference stack.
So the honest phrasing of “Seedance 2.0 ComfyUI support” is: ComfyUI can be the interface, but somebody’s API key pays for every frame. If your reason for wanting ComfyUI was avoiding per-clip costs, this route does not deliver it. If your reason was pipeline integration — chaining Seedance output into upscalers, interpolation or compositing you run locally — it works fine, and our Seedance API guide covers the billing model you will be plugging into.
What “closed” actually costs you
Three practical consequences follow, and none of them is the one people usually worry about.
You cannot run it offline or air-gapped. Every generation leaves your machine. For agencies handling client footage under NDA, or anyone working with unreleased product imagery, that is a procurement question rather than a preference, and no amount of third-party tooling changes it.
Your usage rights come from a terms-of-service document, not a model licence. With an open-weight model you read one licence file and know where you stand for the lifetime of that download. With Seedance, the rights attached to what you generate are defined by whichever platform you generated on — Dreamina, BytePlus ModelArk, or a reseller — and those terms can be revised without a version number changing. Check the terms of the specific platform you are on before building a commercial workflow on it.
Nothing is preserved if a route closes. A downloaded checkpoint keeps working after a vendor changes its mind; API access does not. That is the same fragility we documented when third-party “Seedance 2.5 access” claims outran what platforms would actually confirm.
What “closed” does not mean: it does not mean the output is unusable commercially, and it does not mean you are doing anything irregular by using it. Plenty of production work runs on closed models. It only means the terms live somewhere other than a LICENSE file.
ByteDance publishes weights — just not these
It would be wrong to read this as “ByteDance doesn’t do open weights.” It does, routinely, and that is what makes the Seedance silence a deliberate product decision rather than a policy.
On August 15, 2026 the two ByteDance Hugging Face organisations hosted, among their 116 public model repositories, ByteDance-Seed/SeedVR2-3B and SeedVR2-7B (video restoration), ByteDance/SDXL-Lightning and ByteDance/AnimateDiff-Lightning (image and animation acceleration), ByteDance-Seed/Seed-OSS-36B-Base, the UI-TARS family and ByteDance-Seed/Seed-Coder-8B-Instruct. On GitHub, ByteDance-Seed/Bagel is described in the organisation’s own words as an “Open-source unified multimodal model.”
So the company ships open weights when the model is a research contribution or an ecosystem play, and withholds them when the model is the product being metered. Seedance is the product being metered. A Tech Times headline dated July 31, 2026 framed the same split — “China’s AI Video Battle Picks Sides: Seedance 2.5 Stays Closed, MiniMax H3 Goes Open” — though we cite it as a third-party headline only, because the article body returned HTTP 403 to our fetch on August 15, 2026 and we did not read it.
On the rumour question, we will state the absence precisely rather than manufacture a conclusion: we found no ByteDance statement announcing a future open-weight Seedance release, and no ByteDance statement ruling one out. Third-party posts predicting one are predictions. If that changes, it will appear first as a repository under one of the two organisations linked above — which is exactly why the five-minute check below is worth knowing.
If you need a model that runs on your hardware
For the readers whose real question was “how do I generate video locally,” Seedance is simply the wrong shopping list. These were the download counts on Hugging Face on August 15, 2026:
| Model | Licence field | Downloads |
|---|---|---|
MiniMaxAI/MiniMax-H3 | other — minimax-h3-community-license-agreement | 1,997,541 |
Lightricks/LTX-Video | other | 559,711 |
Wan-AI/Wan2.2-TI2V-5B-Diffusers | apache-2.0 | 195,127 |
Comfy-Org/Wan_2.2_ComfyUI_Repackaged | not stated on the repository | 4,849,232 |
Comfy-Org/MiniMax-H3 | other | 11,768,622 |
Two things to read carefully before you commit. First, the licence column is not decoration: only the Wan 2.2 entry above carries a standard open-source licence. MiniMax-H3 ships under a bespoke community agreement, and other is Hugging Face’s way of saying “read the actual document.” Second, the repackaged Comfy-Org builds carry by far the largest download numbers because they are the ComfyUI-ready form of the same weights — which is the concrete difference from Seedance: for these models, a “ComfyUI node” implies a file you download, and the download counts prove people are downloading it.
We have not benchmarked any of these against Seedance ourselves, and the figures above are availability and licence facts rather than quality judgements — a downloadable model is not automatically a better one. What they establish is only this: for these models the phrase “run it locally” describes something that exists.
How to check this yourself in five minutes
Model availability changes. The method does not, and it is worth having because the answer you get from a search engine on this topic is frequently written by someone selling API credits.
- Check the publisher’s own accounts, not a search box. Open
huggingface.co/ByteDanceandhuggingface.co/ByteDance-Seedand look for the model by name. A vendor that has released weights does not hide them from its own organisation page. - Treat search results as claims, not evidence. Any account can create a repository with any name. Open the Files tab: a real model repository contains
.safetensors,.bin,.ptor.gguffiles measured in gigabytes. A README and a.gitattributesare a landing page. - Read the download counter. A genuinely public video model accumulates hundreds of thousands of downloads within weeks. Zero downloads on a repository named after a famous model means there is nothing to download.
- For ComfyUI, check which directory the node lives in. Nodes under
comfy_api_nodes/call a remote service and bill you. Nodes undercomfy_extras/load weights from disk. If a custom node pack’s description contains the words “API key,” that settles it before you install anything. - Distrust the phrase “open source” in a headline. Ask which of the three things is being claimed — code, weights, or local execution — and check that one specifically.
Applied to Seedance on August 15, 2026, all five checks return the same result. If ByteDance changes course, step 1 will show it before any article does.
Related Content
- Where to Access Seedance 2.0: Every Channel & Region — the full matrix of official channels versus resellers, since API access is the only route
- Seedance API Guide — model IDs, token billing and per-video rates for the route this page concludes you are stuck with
- Is Seedance 2.0 Free? — why “no public weights” is the structural reason the free-Seedance sites cannot be what they claim
- Seedance Official Website vs the Clones — how to identify a Seedance-branded domain before trusting it
- Seedance 2.0 Pricing: Plans, Credits & Costs — what the metered route actually costs
SeedanceTips is an independent publication. We are not affiliated with, sponsored by, or endorsed by ByteDance, Hugging Face, Comfy Org, or any of the third-party projects named on this page, and this article contains no affiliate links. Every repository listing, file manifest, download count, HTTP status and source-code reference above was read by us on August 15, 2026. Model availability changes without notice — re-run the five checks above before relying on any of it.