Help Center/Admin Operations/Upload and manage files in the Media Library
Admin Operations•Last updated: 2026-10-20•4 min read

Upload and manage files in the Media Library

The Media Library stores validated images and PDFs in the database, shows where each file is used, and removes files safely.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

In the admin sidebar open "Universal Studio" then "Media Library" (/admin/studio/media). The tiles show Active files, Removed files and Active storage.

2

Upload a file

Use "Upload a file" above the table. PNG, JPEG, GIF, WebP or PDF up to 4 MB are accepted. The server reads the file type from the file itself, so a renamed file is refused, and SVG is never accepted. The message shows the file link (/api/v1/media/<id>) to use as an article cover image. Uploading the exact same file again returns the existing one.

3

Read the table

Each row shows the file name (cleaned of paths and markup), type, size, status, what uses it ("Used by": articles and handbooks, or "Not used"), the uploader, the date, the SHA-256 and the link.

4

Remove a file

Click the trash icon and give a reason. Removal is a status change to REMOVED and the public link stops working. A file that an article or handbook still uses is refused and the message says what uses it.

5

Purge for good

On a REMOVED file that nothing references, click "Purge for good" and confirm. This permanently erases the file and cannot be undone. Any other file is refused.

Expected Operational Outcome

Uploaded files get a working link; removed files stop being served; purged files are gone.

Troubleshooting & Failure Modes

Symptom: The upload is refused as an unsupported type
Likely Cause: The file bytes are not PNG, JPEG, GIF, WebP or PDF (for example an SVG or a renamed file).
Resolution: Export the image as PNG or JPEG and upload that.
Symptom: The page says tables are not created
Likely Cause: The Studio tables are not applied in this database.
Resolution: An operator runs "npm run db:apply:studio".

Was this guide helpful?

Help us refine our platform documentation