# HF Space "Static SDK is not supported" **URL:** \ **Category:** Spaces\ **Created:** [February 7, 2026, 10:39am UTC](https://discuss.huggingface.co/t/hf-space-static-sdk-is-not-supported/173178 "2026-02-07T10:39:14Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [February 11, 2026, 5:38am UTC](https://discuss.huggingface.co/t/hf-space-static-sdk-is-not-supported/173178/6 "2026-02-11T05:38:09Z")
The below long output is purely a general observation. Personally, when encountering frequent minor yet peculiar errors like this, I’ve found it wise to also consider the possibility that the site is undergoing some changes, causing unstable behavior, or that some incorrect flags are set in the space… (When caused by incorrect flags, the same code often runs without issues in a separately created space. For caching issues, creating a separate space is usually the simplest fix.)🤔 * * * ## What that error actually means On Hugging Face Spaces, **“Static SDK is not supported” is a _configuration-layer_ failure** , not a “your JS crashed” runtime failure. It typically appears when the Hub **can’t (or won’t) apply `sdk: static` for that Space**, so it falls back to a generic “configuration error” page (the one that shows the “Base README.md template”). You can see the exact same config-error page pattern in other public Spaces, e.g. `lmarena-ai/lmarena-leaderboard` and `victor/sveltekit-space`. ([Hugging Face](https://huggingface.co/spaces/lmarena-ai/lmarena-leaderboard "LMArena Leaderboard - a Hugging Face Space by lmarena-ai")) * * * ## Is `app_build_command` required? No. Hugging Face supports two “static” modes: 1. **Commit built assets** (your approach): you push `dist/` and set `app_file` to the HTML entry point. 2. **Build on Hugging Face** : you set `app_build_command`, and HF runs it on updates, then serves the output. ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-sdks-static "Static HTML Spaces - Hugging Face")) So the absence of `app_build_command` is only a problem if **`dist/index.html` is missing or wrong**. In _your_ repo, the config is present and correctly formatted as front-matter, and `dist/index.html` exists. ([Hugging Face](https://huggingface.co/spaces/HPAI-BSC/TuRTLe-Leaderboard/blob/main/README.md?code=true "README.md · HPAI-BSC/TuRTLe-Leaderboard at main")) * * * ## Can you see logs for this kind of failure? ### 1) Where logs normally are For “normal” (container-based) Spaces, HF exposes logs via the **Logs tab / Logs UI**. ([Hugging Face Forums](https://discuss.huggingface.co/t/debugging-spaceses-application/71242 "Debugging Spaceses Application - Spaces")) ### 2) What that means for Static Spaces A pure static Space **does not run an app server** , so there are typically: - **no container runtime logs** , because there’s no long-running container - **only build logs if you use `app_build_command`** (because then HF actually runs a build job) ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-sdks-static "Static HTML Spaces - Hugging Face")) When you’re in **Configuration error** , you often won’t get meaningful “logs” because the platform is failing _before_ a build/run phase starts. * * * ## The most common causes (and fixes) ### Cause A — The Space is in a mode that Static doesn’t support (most likely in Gradio→Static migrations) Two settings are frequent culprits: #### A1) ZeroGPU still enabled HF’s ZeroGPU doc explicitly says: **“ZeroGPU Spaces are exclusively compatible with the Gradio SDK.”** ([Hugging Face](https://huggingface.co/docs/hub/spaces-zerogpu "Spaces ZeroGPU: Dynamic GPU Allocation for Spaces")) **Fix** - Space **Settings → Hardware** - Switch **away from ZeroGPU** to a CPU tier (or dedicated GPU), then rebuild/restart. #### A2) Dev Mode enabled HF Dev Mode doc explicitly says: **Dev Mode is not available for static Spaces.** ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-dev-mode "Spaces Dev Mode: Seamless development in Spaces")) **Fix** - Space **Settings → Dev Mode** - Disable it, then rebuild/restart. **Why it “worked for 2 days”** These settings can look fine until a rebuild/restart/validation pass happens (sleep/wake, infra reschedule, manual restart), then the platform enforces the incompatibility and flips to config error. * * * ### Cause B — HF is not actually using your README config (YAML parsing / precedence issues) HF reads Space config from the **YAML front-matter block at the very top of README**. ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-config-reference "Spaces Configuration Reference")) Common pitfalls: - Anything (badges, headings) above the `---` block - Putting the YAML inside a markdown code fence - YAML becoming invalid after an edit In your current `README.md`, the front-matter _looks correct_ in the file view. ([Hugging Face](https://huggingface.co/spaces/HPAI-BSC/TuRTLe-Leaderboard/blob/main/README.md?code=true "README.md · HPAI-BSC/TuRTLe-Leaderboard at main")) Still, if you edited via UI and introduced invisible formatting issues, it can cause intermittent “config not applied” behavior. **Fix** - Ensure the README starts exactly like this (first byte of file is the first `-`): - Commit a small change to the YAML block (e.g. toggle `pinned`), push, then revert (forces config re-evaluation). * * * ### Cause C — Static build steps may be paywalled in some situations Hugging Face’s static docs describe `app_build_command` as supported. ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-sdks-static "Static HTML Spaces - Hugging Face")) However, multiple public Spaces currently show a **configuration error stating** : > “Static space builds require a paid plan. Subscribe to Team or Enterprise …” ([Hugging Face](https://huggingface.co/spaces/paloma-tfrere/fontmap "Fontmap - a Hugging Face Space by paloma-tfrere")) So: - **Static without `app_build_command`** : generally works as simple hosting (your approach). - **Static with `app_build_command`** : may trigger the paid-plan gate in some accounts/orgs (based on the error HF itself shows). ([Hugging Face](https://huggingface.co/spaces/paloma-tfrere/fontmap "Fontmap - a Hugging Face Space by paloma-tfrere")) If you add `app_build_command` just to “get logs”, you might hit that gate. **Workarounds if you need reproducible builds without HF build** - Build in CI and commit/push `dist/` (what you’re doing) - HF’s own blog suggests a “two-space” pattern: a Docker “builder” Space that builds and deploys to a static “site” Space. ([Hugging Face](https://huggingface.co/blog/severo/build-static-html-spaces "Build static HTML spaces")) * * * ### Cause D — Platform-side regression/outage (less common, but real) When very large/high-profile Spaces also show “Static SDK is not supported”, it can indicate an HF-side regression rather than your repo (example: `lmarena-ai/lmarena-leaderboard` showing the same configuration error page). ([Hugging Face](https://huggingface.co/spaces/lmarena-ai/lmarena-leaderboard "LMArena Leaderboard - a Hugging Face Space by lmarena-ai")) **What you can do** - Apply the fixes in A/B first (they’re quick and within your control) - If still broken, open a forum thread with: * * * ## What I would do for _your_ Space (ordered, fastest signal first) 1. **Check Settings → Hardware** If it’s **ZeroGPU** , switch to CPU. (Static + ZeroGPU is incompatible.) ([Hugging Face](https://huggingface.co/docs/hub/spaces-zerogpu "Spaces ZeroGPU: Dynamic GPU Allocation for Spaces")) 2. **Check Settings → Dev Mode** If enabled, disable it. (Static + Dev Mode is unsupported.) ([Hugging Face](https://huggingface.co/docs/hub/en/spaces-dev-mode "Spaces Dev Mode: Seamless development in Spaces")) 3. **Force a config refresh** 4. **Do not add `app_build_command` just for troubleshooting** unless you’ve confirmed your org/account won’t hit the “static build requires paid plan” gate. ([Hugging Face](https://huggingface.co/spaces/paloma-tfrere/fontmap "Fontmap - a Hugging Face Space by paloma-tfrere")) 5. If it still flips back after a day or two: Create a **brand-new Static HTML Space** under the same org and push only a minimal `dist/index.html` + README front-matter. If _that_ also breaks, it strongly points to **org-level restrictions or HF-side behavior** , not your app bundle. * * * ## Good references and similar cases - **Official docs** - **Logs / debugging** - **Similar failures** If you want the single most likely fix given “Gradio → Static” + “works, then breaks after ~2 days”: **ZeroGPU or Dev Mode still enabled in Settings** (static-incompatible), with the failure surfacing on a rebuild/revalidation. ([Hugging Face](https://huggingface.co/docs/hub/spaces-zerogpu "Spaces ZeroGPU: Dynamic GPU Allocation for Spaces")) --- _[View the full topic](https://discuss.huggingface.co/t/hf-space-static-sdk-is-not-supported/173178)._