Forge Spaces: Install, Launch, Stop, and Remove Mini-Apps
The Spaces tab runs adapted Hugging Face demos beside Forge. Each one has a separate download chain, model cache, local server, and failure surface.
A Space is local code—not a harmless embedded webpage.
Forge includes built-in wrappers under Spaces. Install fetches a pinned Hugging Face Space version. Launch then imports Python in the Forge process, unloads main Forge models, may fetch additional model repositories, and opens another Gradio server.
Remote dependencies and hardware requirements differ between Spaces. Check the selected Space before installing it, and start with one Space at a time.
Record four boundaries before downloading.
“Built in” describes the wrapper shipped in Forge. It does not mean its remote code, models, package set, or hardware outcome is frozen forever.
Repository
Write down the Space repo_id and pinned revision. A similarly named demo elsewhere is not this wrapper.
Storage
Measure the mirror and [MODELS]/diffusers separately. Uninstall affects only the first bucket.
Network
Install and first Launch are distinct fetch phases. Keep the console visible until the mini-app URL appears.
Exposure
If Forge uses --listen, the Space inherits that bind address but not the main auth/TLS arguments.
Read the state before pressing the next button.
This explainer mirrors the current manager; it does not control your Forge session. Use the real console and status label as test.
Install
Creates huggingface_space_mirror, downloads the pinned Space version, then runs the wrapper requirements.txt when one exists.
Keep the console open. “Install finished” is stronger details than the button returning.
Launch
Unloads Forge models, changes the process working directory to the mirror, imports forge_app.py, and lets that wrapper resolve additional models.
Wait for a separate local URL. First Launch can download much more than Install.
Terminate
Runs another Gradio server in a thread on the first free port at or above the main Forge port.
Closing the browser tab does not flip is_running. Use Terminate and wait for the running URL to disappear.
Uninstall
Recursively removes only that Space mirror. Shared model cache and pip packages are not rolled back.
Export wanted outputs before removal, then measure both the mirror and [MODELS]/diffusers if disk recovery is the goal.
- 01
Open the console
Do not install from a detached or hidden launcher window.
- 02
Install one Space
Wait for the pinned version and any pip step to finish.
- 03
Launch once online
Let secondary models resolve; save the first traceback if they do not.
- 04
Use one known input
Do not combine a new Space, model, and network change in one test.
- 05
Export results
Copy wanted files outside the mirror before removal.
- 06
Terminate, then uninstall
Confirm the running URL closes before recursively deleting the mirror.
A second port can bypass assumptions about the first.
The manager reuses gradio_server_name(). With default local startup that resolves locally; with --listen it resolves to 0.0.0.0. The separate demo.launch() call receives no main Forge auth, TLS, allowed-path, or root-path arguments.
Operational boundary: do not expose Forge Spaces to a LAN or the internet merely because the main UI has a password. Verify the actual Space port independently.
Review network flagsNine wrappers, nine download surfaces.
Search by task, repository, model family, or warning. Every card remains in the initial HTML and links to the exact wrapper metadata.
Showing all 9 version-specific Spaces
Animagine XL 3.1
Anime-focused SDXL text-to-image, optional img2img upscale, styles, and wildcards.
- Pinned version
cagliostrolab/animagine-xl-3.1@f2400163↗- Launch fetches
- Animagine XL single-file checkpoint, SDXL VAE fix, and a custom Diffusers pipeline can be resolved through Hugging Face on first launch.
- Storage
- Space mirror plus shared models/diffusers cache; its relative ./outputs directory lives under the mirror while the Space runs.
- Boundary
- The code explicitly says its demo does not work on CPU. This is a separate SDXL pipeline, not the checkpoint selected in Forge txt2img.
BiRefNet
Background removal for a single image, folders, video, and—when available—webcam input.
- Pinned version
not-lain/background-removal@16bb0ccc↗- Launch fetches
- Loads ZhengPeng7/BiRefNet_HR with Transformers and trust_remote_code=True; video mode also depends on MoviePy being importable.
- Storage
- Pinned Space mirror plus model files in the shared Hugging Face cache.
- Boundary
- Downloaded model-repository Python can execute because trust_remote_code is enabled. Video capability is conditional in code and is not guaranteed by Install status.
Florence-2
Captions, OCR, object detection, phrase grounding, region proposals, and segmentation.
- Pinned version
gokaygokay/Florence-2@9ff9f99d↗- Launch fetches
- Loads both microsoft/Florence-2-large and microsoft/Florence-2-base models and processors with trust_remote_code=True.
- Storage
- Pinned demo mirror plus both Florence model families in the shared models/diffusers cache.
- Boundary
- Launch imports two model sizes before the mini-app is ready. Install completion therefore does not prove the first Launch can finish offline or fit the device.
GeoWizard
Produces a depth visualization and surface-normal map from one image.
- Pinned version
lemonaddie/geowizard@e25e940c↗- Launch fetches
- Loads VAE, scheduler, image encoder, feature extractor, and UNet directly from the pinned Space mirror.
- Storage
- Its large pipeline version and example files live in the Space mirror; generated relative files can live there too.
- Boundary
- Results can vary by hardware, model, and input. Start with a small job and increase complexity only after the Space runs successfully.
IC-Light
Relights a foreground with text or a background condition using the foreground IC-Light model.
- Pinned version
lllyasviel/IC-Light@3072485a↗- Launch fetches
- Uses the mirror IC-Light offset plus stablediffusionapi/realistic-vision-v51 and briaai/RMBG-1.4 from Hugging Face.
- Storage
- Pinned Space mirror plus shared Hugging Face cache entries for the base model and background remover.
- Boundary
- The embedded pipeline sets safety_checker=None. It is independent from the main Forge checkpoint and its safety/extension settings.
IDM-VTON
Virtual garment try-on using a person image, clothing image, pose, parsing, and an SDXL inpaint pipeline.
- Pinned version
yisol/IDM-VTON@810e5908↗- Launch fetches
- The only current Space with a root requirements.txt; Install runs pip for basicsr, fvcore, pycocotools, av, and other packages, then Launch resolves IDM-VTON components.
- Storage
- Mirror, shared model cache, and packages installed into the same Forge Python environment.
- Boundary
- Uninstall removes the mirror but does not roll back pip packages. Open reports document missing-weight and pose-index failures; there is no universal fix.
issues #2520 and #2689 describe missing model files, repeated Reinstall state, and pose preprocessing failure.
IllusionDiffusion
Creates pattern- or QR-conditioned Stable Diffusion 1.5 illusion images.
- Pinned version
AP123/IllusionDiffusion@7a874d15↗- Launch fetches
- Resolves a Realistic Vision base, SD VAE, Monster Labs QR ControlNet, and optionally a safety checker and CLIP processor.
- Storage
- Pinned Space mirror plus several shared Diffusers model repositories.
- Boundary
- SAFETY_CHECKER defaults to off in the current wrapper. This is not the integrated Forge ControlNet panel and does not use its selected model.
PhotoMaker V2
Identity-preserving portrait generation from one or more face images, with optional sketch conditioning.
- Pinned version
TencentARC/PhotoMaker-V2@745c135a↗- Launch fetches
- Downloads the PhotoMaker V2 adapter, SDXL T2I adapter, RealVisXL base, and face-analysis assets through Hugging Face or their libraries.
- Storage
- Pinned Space mirror plus multiple shared model-cache entries.
- Boundary
- Earlier reports show dependency and removed-argument failures. A maintainer updated the targeted revision in 2025; old manual patches are not a standing instruction.
#2393, #2251, and discussion #2656 record Accelerate and Diffusers compatibility failures across earlier builds.
Sapiens Normal
Human foreground segmentation followed by surface-normal estimation with selectable Sapiens model size.
- Pinned version
facebook/sapiens_normal@9c0e1ffc↗- Launch fetches
- The pinned version excludes *.pt2, then the wrapper downloads segmentation and selected normal-estimation checkpoints from the Space main branch.
- Storage
- Downloaded TorchScript checkpoints are stored inside the mirror assets/checkpoints directory.
- Boundary
- Checkpoint URLs target the remote main branch rather than the pinned revision. Availability and bytes can therefore change independently of the Forge commit.
Remove a product name or switch to All. The name may belong to an extension, a fork, or a newer repository state.
Uninstall is not a full rollback.
Four storage layers answer four different cleanup questions. Delete only after resolving the active install profile and making a backup.
[PROGRAM]/extensions-builtin/forge_space_[name]/Forge-owned wrapper and metadata. Normal Space Uninstall does not remove it.
Resolve [PROGRAM] ↗[WRAPPER]/huggingface_space_mirror/Install creates it; Uninstall recursively deletes it. Relative Space outputs can be inside it.
[MODELS]/diffusers/Secondary Hugging Face models can remain and may be shared by another Space or extension.
Forge venv or package system/pythonA Space requirements.txt can add packages here. Mirror deletion does not uninstall them.
Locate the environment ↗Before Uninstall: terminate the Space, export outputs, save the console checklist, and confirm the target mirror belongs to that Space. Never recursively delete the broad models or program root.
Preserve the first error.
Repeated Install clicks overwrite useful state without identifying whether the failure belongs to version, package, model, device, or port.
Install stops before “Install finished”
Record the Space name, Forge commit, repo revision, first console exception, free disk, and whether Hugging Face is reachable. A created mirror can still make the UI appear installed. Terminate nothing, use Uninstall once, then retry only after the cause changes.
Launch fails while importing a model or module
Separate a missing module from a missing model file and from a CUDA operation. Do not broadly upgrade Diffusers, Transformers, Accelerate, or Torch: Forge pins a shared environment. Check the exact issue state for your commit before making one reversible change.
PhotoMaker V2 shows an Accelerate or resume_download error
Earlier reports #2251/#2393 and discussion #2656 describe different dependency states. A maintainer later changed Forge pins and the targeted Space revision. Update the correct fix depends on the Forge version; do not apply an old manual code deletion as a universal fix.
IDM-VTON reports a missing weight or pose index
Issues #2520 and #2689 remain community reports, not a confirmed repair recipe. Save the full traceback and input conditions. Reinstall cannot manufacture a file absent from the referenced repository or repair an input with no detected pose.
The browser opened, but the Space URL is unreachable
Use the exact running URL printed in the Spaces label and console. Check the selected port, bind address, firewall, proxy, container forwarding, and whether the worker thread printed a later exception. Do not assume the main Forge URL and Space URL share a route.
VRAM was freed and Forge reloads its checkpoint later
This is consistent with the manager: Launch calls unload_all_models(), and Space GPU wrappers clean cache around work. Terminate the Space before returning to a controlled Forge benchmark; a later checkpoint reload does not guarantee a memory leak.
Answers before the first download.
Questions combine the local documentation corpus, current code review, owner announcements, and earlier user failures. Unsupported hardware outcomes remain untested.
What is the Spaces tab in Stable Diffusion WebUI Forge?
It is an experimental launcher for local mini-apps adapted from Hugging Face Spaces. Each entry has its own wrapper, pinned Space version, interface, dependencies, models, and local Gradio server. It is not a gallery of web links and not the normal txt2img pipeline.
Which Forge Spaces are included?
The current clean Forge commit exposes nine: Animagine XL 3.1, BiRefNet, Florence-2, GeoWizard, IC-Light, IDM-VTON, IllusionDiffusion, PhotoMaker V2, and Sapiens Normal. A tenth forge_space_example directory is disabled by configuration and is not counted.
What does the Install button download?
It creates the Space huggingface_space_mirror directory and downloads the repo_id at the revision in space_meta.json. If the built-in wrapper has requirements.txt, Install also runs pip against the active Forge Python environment.
Why does Launch download more files after Install finished?
Install fetches the pinned Space version. forge_app.py can then call from_pretrained, hf_hub_download, or direct URLs for base models, adapters, processors, and checkpoints. Those secondary fetches are a separate phase.
Where are Forge Space files stored?
The pinned version lives under the built-in Space directory in huggingface_space_mirror. Hugging Face model cache is redirected to the Forge models/diffusers directory. Relative outputs can be created inside the mirror because Launch changes the process working directory there.
Does Uninstall remove every downloaded model?
No. The manager deletes the Space mirror and explicitly warns that models/diffusers can remain because those cache entries may be reused. It also does not uninstall Python packages added to the shared Forge environment.
Will Uninstall delete my Space outputs?
It can. The manager recursively removes the mirror, and some wrappers use relative output directories while the process working directory is that mirror. Export files you care about before clicking Uninstall.
Why does IDM-VTON still show Reinstall after installation?
For a Space with requirements.txt, the current UI deliberately labels the enabled Install button “Reinstall” whenever the mirror exists. That label alone is not an error. Use the console and Launch result to determine whether installation is complete.
Why does a Space say Installed but fail to launch?
The installed check only tests whether huggingface_space_mirror exists. A partial version, failed pip step, unavailable secondary model, dependency mismatch, unsupported device operation, or remote-code error can therefore fail later. Capture the first traceback before changing anything.
Does Forge Spaces work offline?
Not reliably from Install status alone. A Space may need its pinned version, secondary model repositories, direct checkpoint URLs, and remote Python modules during first Launch or first use. Offline operation is only established after that exact Space and task complete with network access blocked.
Can Forge Spaces use my normal checkpoint folder?
Do not assume so. These wrappers construct their own Diffusers or Transformers pipelines and resolve named repositories through the shared Hugging Face cache. The checkpoint selected in the main Forge header usually does not control them.
Why does a Space open on port 7861 or another port?
The manager starts at the configured Forge port, tests ports in sequence, and chooses the first free one. If the main UI owns 7860, the first Space commonly receives 7861, but the actual console URL is authoritative.
Does closing the Space browser tab stop it?
No. Browser closure is not wired to the manager state. Return to Forge → Spaces, press Terminate, and wait until the entry returns to “Installed, Ready to Launch”.
Is a Forge Space sandboxed from the rest of Forge?
No. The wrapper executes Python in the same process, temporarily changes process-wide cwd and sys.path, can install packages into the active environment, and shares GPU and model-cache state. Some wrappers explicitly enable trust_remote_code.
Is a launched Space protected by my Forge password?
The current Space launch call does not forward the main Gradio auth or TLS arguments. It reuses the server binding name, so --listen or a custom server name can expose the separate Space port without the protection you expected from the main UI. Keep Forge local unless you have independently secured every port.
Can I run several Forge Spaces at once?
The UI does not enforce a global one-Space limit, but the implementation shares process-wide cwd, sys.path, module names, model cache, and GPU management. this guide does not guarantee concurrent use; run one at a time when diagnosing or protecting work.
Do all Spaces support CPU, AMD, or macOS?
No support matrix is established by the current code. Several wrappers call CUDA directly, use float16, or state that CPU is unsupported. Treat a successful Install as no hardware guarantee and preserve the exact first error.
Can I install any Hugging Face Space into this tab?
There is no confirmed end-user “paste any Space URL” workflow. Forge identifies an extension as a Space only when it has both space_meta.json and forge_app.py, and the wrapper must integrate with the local spaces runtime. Copying arbitrary remote code into extensions is a developer and security task, not a normal install step.