Uploading files

Large files & chunked uploads

Split a file into parts, send each part to CDNForge, then complete the upload. The server binds size, MIME type, storage target, and public id to an upload session so clients cannot override those values at the end.

When to use chunked uploads

• Files that are too large to send as one multipart body through a serverless request limit.
• Video and audio from integrations that always prefer chunked (including the official FiveM resource).
• Same-origin uploads when you do not want to depend on storage CORS for a client PUT.

For browser or NUI flows that can PUT directly to storage, presigned URLs remain a valid alternative.

Size limits

Two API families

• Media — /api/v1/upload/chunked/* with cnf_img_, cnf_vid_, or cnf_aud_.
• Generic files — /api/v1/file/chunked/* with cnf_fil_ only. Bytes are stored as-is (no image compression).

Flow

1. Init — declare filename, MIME type, and total size. CDNForge creates a session and returns uploadId.
2. Part — upload each chunk as multipart form data with the session id and part number.
3. Complete — send only the uploadId. The session supplies public id, MIME, size, and storage target.

1) Init

curl -X POST https://app.back2rp.org/api/v1/upload/chunked/init \
  -H "Authorization: Bearer cnf_vid_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "filename": "clip.mp4",
    "mimeType": "video/mp4",
    "size": 18432000
  }'

{
  "uploadId": "V1StGXR8_Z5jdHi6B-myT",
  "publicId": "abc123xyz.mp4",
  "mimeType": "video/mp4",
  "originalName": "clip.mp4",
  "storageBucket": "cdnforge-media",
  "partSize": 4194304,
  "expiresAt": "2026-08-31T23:00:00.000Z"
}

Optional fields on init: folder, folderId, and metadata. They are stored on the session and applied when the upload completes.

2) Upload parts

Multipart form fields: uploadId, partNumber (starts at 1), and chunk (the binary part).

curl -X POST https://app.back2rp.org/api/v1/upload/chunked/part \
  -H "Authorization: Bearer cnf_vid_your_key" \
  -F uploadId="$UPLOAD_ID" \
  -F partNumber=1 \
  -F chunk=@part1.bin

{
  "ok": true,
  "partNumber": 1,
  "size": 4194304
}

• Use the partSize from init (4 MB) for all but possibly the last part.
• Parts that would exceed the declared total size return HTTP 413.
• Invalid or missing chunks return HTTP 400.

3) Complete

Send only the session id. Do not send publicId, mimeType, size, or storageBucket on complete — the API ignores client overrides and uses the upload session.

curl -X POST https://app.back2rp.org/api/v1/upload/chunked/complete \
  -H "Authorization: Bearer cnf_vid_your_key" \
  -H "Content-Type: application/json" \
  -d '{"uploadId":"V1StGXR8_Z5jdHi6B-myT"}'

{
  "id": "fil_...",
  "url": "https://cdn.back2rp.org/u/abc123xyz.mp4",
  "publicId": "abc123xyz.mp4",
  "size": 18432000,
  "mimeType": "video/mp4",
  "originalName": "clip.mp4"
}

Generic file chunked routes

Same protocol with a file key and the /api/v1/file/chunked/* paths:

• POST /api/v1/file/chunked/init
• POST /api/v1/file/chunked/part
• POST /api/v1/file/chunked/complete

curl -X POST https://app.back2rp.org/api/v1/file/chunked/init \
  -H "Authorization: Bearer cnf_fil_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "filename": "pack.zip",
    "mimeType": "application/zip",
    "size": 52428800
  }'

Errors & retries

The official FiveM resource retries 429/5xx up to three times and keeps at most two uploads in flight. Custom clients should retry transient failures on the same session and part number.

Sessions expire

Pending sessions expire after the TTL (default one hour). Expired sessions return HTTP 410. Start a new init if that happens; previous parts for that session are no longer usable.