> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nonefivem.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Storage & CDN

NoCloud Storage provides a powerful and globally distributed public file storage solution designed specifically for game developers. Combined with our integrated CDN, your content is always fast, reliable, and accessible worldwide.

## Overview

Our storage platform is built for serving public content with maximum performance:

<CardGroup cols={2}>
  <Card title="Public File Storage" icon="folder-open">
    Upload and serve public files like images, screenshots, and game assets with
    simple API calls.
  </Card>

  <Card title="Global CDN" icon="globe">
    Deliver content lightning-fast with our worldwide content delivery network,
    ensuring low latency for players everywhere.
  </Card>
</CardGroup>

<Note>
  NoCloud Storage is designed for **public files only**. All uploaded files are
  publicly accessible via CDN URLs. Do not upload sensitive or private data.
</Note>

## Key Features

### Public File Hosting

* **Instant Availability** — Files are immediately available via CDN after upload.
* **Permanent URLs** — Each file receives a unique, permanent URL that never changes.
* **Multiple Formats** — Support for images, audio, and other common file types.

### High-Performance CDN

* **Global Edge Network** — Content is cached at edge locations worldwide, reducing latency for players in any region.
* **Smart Caching** — Intelligent cache management ensures players always receive content quickly.
* **Unlimited Bandwidth** — No bandwidth fees — you only pay for storage, not delivery.

### Developer-Friendly

* **Simple API** — RESTful API endpoints make uploading and retrieving files straightforward.
* **SDK Support** — Native SDKs for CFX (FiveM/RedM) and Node.js handle uploads and URL generation for you.
* **Direct URLs** — Get direct CDN URLs for immediate use in your game or application.

## Use Cases

<AccordionGroup>
  <Accordion title="Screenshots & Photos" icon="camera">
    Let players capture and share in-game screenshots. Perfect for polaroid scripts, galleries, and social features.
  </Accordion>

  <Accordion title="Custom Assets" icon="image">
    Host custom images, logos, and visual assets that need to be accessible from
    your game client.
  </Accordion>

  <Accordion title="User-Generated Content" icon="users">
    Allow players to upload and share content like crew logos, custom images, and
    more.
  </Accordion>

  <Accordion title="Shared Media" icon="share-nodes">
    Store and serve media files that need to be accessible across multiple servers or applications.
  </Accordion>
</AccordionGroup>

## How It Works

```mermaid theme={null}
sequenceDiagram
    participant Game as Your Game
    participant API as NoCloud API
    participant CDN as Global CDN

    Game->>API: Upload file
    API->>CDN: Distribute to edge
    API-->>Game: Return CDN URL
    Game->>CDN: Request file
    CDN-->>Game: Serve cached file
```

1. **Upload** — Send your file to NoCloud via API or SDK
2. **Distribute** — Your file is stored and distributed across our global CDN
3. **Receive URL** — Get a permanent CDN URL for your file
4. **Serve** — Use the URL anywhere — files are served from the nearest edge location

## Getting Started

Ready to integrate NoCloud Storage into your project? Check out our SDK documentation:

<CardGroup cols={2}>
  <Card title="CFX SDK" icon="gamepad" href="/cloud/sdks/cfx/storage">
    Storage integration for FiveM and RedM
  </Card>

  <Card title="Node.js SDK" icon="node-js" href="/cloud/sdks/nodejs">
    Storage integration for Node.js applications
  </Card>
</CardGroup>

## Pricing

**Start free, scale as you grow.** Get free storage to get started, then pay only for what you use as your needs expand — **bandwidth is always free**. No hidden fees for downloads or CDN delivery, no matter how many times your files are accessed.

### How Billing Works

We take **daily snapshots** of your storage usage throughout the billing period. At the end of each billing cycle (1 month), you're charged based on the **average usage** across all those daily snapshots — not your peak usage.

This means you're not penalized for temporary spikes. If you upload a large batch of files and delete them a few days later, you only pay for the days they were stored.

### Minimum Billable Object Size

Every stored object has a **minimum billable size of 32 KB**. If a file is smaller than 32 KB, it will be calculated as 32 KB for billing purposes. This covers the infrastructure and processing overhead associated with storing and serving each individual object.

<Accordion title="Billing Examples" icon="calculator">
  **Example 1: Steady Growth**

  * Week 1-2: 10 GB stored
  * Week 3-4: 30 GB stored

  Average usage: $(10 \times 14 + 30 \times 14) \div 28 = 20$ GB

  You'd be billed for **20 GB**, not the peak of 30 GB.

  ***

  **Example 2: Temporary Spike**

  * Days 1-25: 5 GB stored
  * Days 26-28: 50 GB stored (big upload)
  * Days 29-30: 5 GB stored (cleanup)

  Average usage: $(5 \times 25 + 50 \times 3 + 5 \times 2) \div 30 \approx 9.5$ GB

  You'd be billed for roughly **9.5 GB**, not the peak of 50 GB.

  ***

  **Example 3: Constant Usage**

  * All 30 days: 15 GB stored

  Average usage: **15 GB**

  Simple and predictable!
</Accordion>

See our [dashboard](https://dash.nonefivem.com) for current usage and plan details.

<Info>
  Need higher storage limits or enterprise features? [Contact
  us](mailto:support@nonefivem.com) for custom plans.
</Info>