# Spaces ZeroGPU: Dynamic GPU Allocation for Spaces
ZeroGPU is a shared infrastructure that optimizes GPU usage for AI models and demos on Hugging Face Spaces. It dynamically allocates and releases NVIDIA RTX Pro 6000 Blackwell GPUs as needed, offering:
1. **Free GPU Access**: Enables cost-effective GPU usage for Spaces.
2. **Multi-GPU Support**: Allows Spaces to leverage multiple GPUs concurrently on a single application.
Unlike traditional single-GPU allocations, ZeroGPU's efficient system lowers barriers for developers, researchers, and organizations to deploy AI models by maximizing resource utilization and power efficiency.
## Using and hosting ZeroGPU Spaces
- **Using existing ZeroGPU Spaces**
- ZeroGPU Spaces are available to use for free to all users. (Visit [the curated list](https://huggingface.co/spaces/enzostvs/zero-gpu-spaces)).
- [PRO users](https://huggingface.co/subscribe/pro) get x8 more daily usage quota, highest priority in GPU queues, and can go beyond their daily quota using pre-paid credits when using any ZeroGPU Spaces.
- **Hosting your own ZeroGPU Spaces**
- Free personal accounts: accounts in good standing (verified email, account older than 30 days) can host up to 2 ZeroGPU Spaces for free.
- PRO accounts: [Subscribe to PRO](https://huggingface.co/settings/billing/subscription) to host up to 10 ZeroGPU Spaces under your account.
- Organizations: [Subscribe to a Team or Enterprise plan](https://huggingface.co/enterprise) to enable ZeroGPU Spaces for all organization members.
## Technical Specifications
ZeroGPU supports two GPU sizes
| GPU size | Backing hardware | Vram | Quota cost |
|---------------------|------------------------------------|------|------------|
| `large` *(default)* | Half NVIDIA RTX Pro 6000 Blackwell | 48GB | 1× |
| `xlarge` | Full NVIDIA RTX Pro 6000 Blackwell | 96GB | 2× |
> [!NOTE]
> See [GPU size selection](#gpu-size-selection) to learn how to use sizes
## Compatibility
ZeroGPU Spaces are designed to be compatible with most PyTorch-based GPU Spaces. While compatibility is enhanced for high-level Hugging Face libraries like `transformers` and `diffusers`, users should be aware that:
- Currently, ZeroGPU Spaces are exclusively compatible with the **Gradio SDK**.
- ZeroGPU Spaces may have limited compatibility compared to standard GPU Spaces.
- Unexpected issues may arise in some scenarios.
### Supported Versions
- **Gradio**: 4+
- **PyTorch**: Almost all versions from **2.8.0** to **latest** are supported
See full list
- 2.8.0
- 2.9.1
- 2.10.0
- 2.11.0
- 2.12.1
- 2.13.0
- **Python**:
- 3.12.12
- 3.10.13
## Getting started with ZeroGPU
To utilize ZeroGPU in your Space, follow these steps:
1. Make sure the ZeroGPU hardware is selected in your Space settings.
2. Import the `spaces` module.
3. Decorate GPU-dependent functions with `@spaces.GPU`.
This decoration process allows the Space to request a GPU when the function is called and release it upon completion.
> [!NOTE]
> The `@spaces.GPU` decorator is designed to be effect-free in non-ZeroGPU environments, ensuring compatibility across different setups.
### Example Usage
```python
import spaces
from diffusers import DiffusionPipeline
pipe = DiffusionPipeline.from_pretrained(...)
pipe.to('cuda')
@spaces.GPU
def generate(prompt):
return pipe(prompt).images
gr.Interface(
fn=generate,
inputs=gr.Text(),
outputs=gr.Gallery(),
).launch()
```
### Model loading
Even though a real GPU is only available inside `@spaces.GPU` functions, models must be placed on `cuda` at the root module level (as shown in the example above).
Lazy-loading or moving models to CUDA inside `@spaces.GPU` is discouraged, as it is significantly less efficient (CUDA transfers are optimized for placements done during startup).
> [!NOTE]
> Loading models on `cuda` at module level works because a PyTorch CUDA emulation mode is enabled outside `@spaces.GPU` functions, allowing CUDA operations without a real GPU. Inside `@spaces.GPU`, real CUDA is used.
## GPU size selection
The default size used by `@spaces.GPU` is `large` (half NVIDIA RTX Pro 6000 Blackwell).
You can explicitly request a full NVIDIA RTX Pro 6000 Blackwell by specifying `size="xlarge"`:
``` python
@spaces.GPU(size="xlarge")
def generate(prompt):
return pipe(prompt).images
```
> [!NOTE]
> - `xlarge` consumes **2×** more daily quota than `large` (e.g. a 45s **effective** task duration consumes 90s of quota)
> - `xlarge` usually means higher queuing probability and longer wait times
> - Only use `xlarge` when your workload truly benefits from the additional compute or memory
## Duration Management
For functions expected to exceed the default 60-second of GPU runtime, you can specify a custom duration:
```python
@spaces.GPU(duration=120)
def generate(prompt):
return pipe(prompt).images
```
This sets the maximum function runtime to 120 seconds. Specifying shorter durations for quicker functions will improve queue priority for Space visitors.
### Dynamic duration
`@spaces.GPU` also supports dynamic durations.
Instead of directly passing a duration, simply pass a callable that takes the same inputs as your decorated function and returns a duration value:
```python
def get_duration(prompt, steps):
step_duration = 3.75
return steps * step_duration
@spaces.GPU(duration=get_duration)
def generate(prompt, steps):
return pipe(prompt, num_inference_steps=steps).images
```
## Compilation
ZeroGPU does not support `torch.compile`, but you can use PyTorch **ahead-of-time** compilation (requires torch `2.8+`)
Check out this [blogpost](https://huggingface.co/blog/zerogpu-aoti) for a complete guide on ahead-of-time compilation on ZeroGPU.
## Usage Tiers
GPU usage is subject to **daily** quotas, per account tier:
| Account type | Included daily GPU quota | Queue priority |
| ------------------------------ | ------------------------ | --------------- |
| Unauthenticated | 2 minutes | Low |
| Free account | 5 minutes | Medium |
| PRO account | 40 minutes (extensible) | Highest |
| Team organization member | 40 minutes (extensible) | Highest |
| Enterprise organization member | 60 minutes (extensible) | Highest |
Included daily quota resets exactly 24 hours after your first GPU usage.
> [!NOTE]
> Remaining quota directly impacts priority in ZeroGPU queues.
### Extending quota with credits
PRO, Team, and Enterprise users can continue using ZeroGPU Spaces beyond their included daily quota by consuming pre-paid credits at the rate of **$1 per 10 minutes** of GPU time.
Once your daily quota is exhausted, any additional GPU usage is automatically billed against your credit balance.
You can add credits from your [billing settings](https://huggingface.co/settings/billing).
## Hosting Limitations
- **Free personal accounts**: Maximum of 2 ZeroGPU Spaces, for accounts in good standing (verified email, account older than 30 days).
- **Personal accounts ([PRO subscribers](https://huggingface.co/subscribe/pro))**: Maximum of 10 ZeroGPU Spaces.
- **Organization accounts ([Team & Enterprise](https://huggingface.co/enterprise))**: Maximum of 50 ZeroGPU Spaces.
By leveraging ZeroGPU, developers can create more efficient and scalable Spaces, maximizing GPU utilization while minimizing costs.
## Recommendations
If your demo uses a large model, we recommend using optimizations like ahead-of-time compilation and flash-attention 3. You can learn how to leverage these with
ZeroGPU in [this post](https://huggingface.co/blog/zerogpu-aoti). These optimizations will help you to maximize the advantages of ZeroGPU hours and provide
a better user experience.
## Feedback
You can share your feedback on Spaces ZeroGPU directly on the HF Hub: https://huggingface.co/spaces/zero-gpu-explorers/README/discussions