Skip to main content
CDN settings control workspace-level configuration for public asset paths. The settings page shows the public URL, cache purge, placeholders, TTL policies and service deletion.

Public URL

Your workspace slug appears in every public file URL. Choose it carefully during setup: the current service does not accept slug changes after onboarding. If you need another public name, contact support before changing scripts or moving assets. A public URL change requires every integration that stores the old URL to be updated.

Permissions

Your organization role controls whether settings are editable. If settings are read-only and you need to change them, ask an organization owner or admin to update your role.

Placeholders

Placeholders are fallback images for missing public CDN objects. When a requested file exists, FiveMesh CDN serves the file normally. When the file does not exist, FiveMesh checks your placeholder patterns. If a pattern matches the requested path, the matching placeholder image is served instead. This is useful for inventory icons, shop images, job logos, vehicle thumbnails, default avatars and other image-heavy FiveM interfaces where a missing file would otherwise show as a broken image.
Placeholders do not create the missing file. Upload the real image when it is ready.

Add a placeholder

1

Open settings

In CDN, open the Settings tab.
2

Create a placeholder

In Placeholders, click Add placeholder.
3

Enter a pattern

Enter the path pattern that should use the fallback image, such as inventory/items/*.
4

Upload the fallback image

Choose the image FiveMesh should serve when a missing object matches the pattern.
5

Save the placeholder

Save the rule. New matching missing-file requests can now return the placeholder image.

Placeholder patterns

Use patterns that match your folder structure. Keep patterns narrow when different folders need different fallback images. A broad pattern can be useful, but it may make unrelated missing images use the same placeholder.
Use placeholders as a graceful fallback, not as a replacement for organizing and uploading the real assets.

Update or delete a placeholder

Use the actions in the Placeholders list to edit the pattern, replace the image or delete the rule. Deleting a placeholder rule stops future fallback responses for that pattern. It does not delete real CDN objects that were uploaded outside the placeholder rule.

Add a TTL policy

1

Open settings

In CDN, open the Settings tab.
2

Add a policy row

Enter a folder path such as phone, tablet, mugshot or uploads.
3

Choose the retention value

Set the value in hours or days. Values can range from 1 hour to 365 days.
4

Save policies

Click Save policies.
TTL policies apply storage expiration to matching files. Removing a policy does not restore files that have already expired. Avoid overlapping paths with conflicting retention rules.

Portal media expiration

The Media expiration setting in Portal > Medias manages the TTL policy for portal/media/. It appears here alongside your other policies. Changes made in either page affect the same rule. This policy applies to existing files and every Portal using this CDN. Older files can become eligible for deletion as soon as you enable or shorten the period. Expiration happens asynchronously; overlapping CDN rules can remove matching files sooner. Disabling Portal’s expiration setting removes only this policy. It does not restore files or remove your other TTL policies. Review Portal media expiration before changing it.

Path rules

  • Do not start a user-facing path segment with ..
  • Use clear folder names that match your scripts or media workflows.
  • Keep temporary media separate from long-lived assets when retention needs differ.
For temporary script media, start with a shorter path policy. Keep durable assets such as inventory icons in a separate path.

Purge cached delivery

Under Purge CDN cache, review the workspace prefix and click Purge workspace. This requires cdn:purge. Purging expires cached responses under the public workspace prefix; it keeps stored objects. Use it after bulk replacements when requests still return older content. This purge applies to FiveMesh CDN files only; to refresh resource downloads, see Cache operations. For specific objects, use the CDN API reference with a Developer API Key.

Delete the CDN service

In Danger zone, click Delete CDN service and type the current workspace slug to confirm. This requires CDN administration access. Public delivery stops immediately. Cleanup removes stored content, and the dashboard shows deletion progress. Export any files you need before confirming. If Cancel deletion is still available, it can restore the service, but it cannot recover objects already removed. Once cleanup completes, deletion can no longer be cancelled.
Deleting a service is different from purging its cache. Purging keeps files; deletion permanently removes content as cleanup progresses.