Content Editing XP

Currently when a image is deleted with relations to a content collection. It just removes the relation without showing any information on where the images might be used on. It happens a lot of our customer, that they delete an image inside the media gallery without realizing they kill the relation for an required image.

We have tons of media content in our Media Library and sometimes we want to delete unused media to conserve space in our server. It would really be helpful if there was a way we could identify the media that are or aren't being used at a quick glance instead of having to check each entry.

Strapi version: v5 --- What I'm asking for The ability to extend the plugin::upload.file collection type with custom fields through the Content-Type Builder — the same way the users-permissions plugin lets you add extra fields to the User collection type. Current behaviour The plugin::upload.file schema is fixed and cannot be extended. The Content-Type Builder does not expose it as an editable type. Workarounds require maintaining a separate shadow collection with a relation back to the file, which complicates queries and means asset metadata lives outside the media library. Expected behaviour The Content-Type Builder shows an "Upload" section alongside other plugin-owned types Developers can add fields to it: text, number, boolean, date, enumeration, relation — the same field types available on any collection type Custom fields appear and are editable in the asset detail panel inside the media library Custom fields are included in Upload API responses alongside the built-in fields Schema changes survive upgrades without manual migration Example custom fields copyright (text) — photo credit line for licensed imagery expiresAt (date) — flag assets that should no longer be used after a campaign ends approvedForMarketing (boolean) — editorial approval toggle for brand assets property (relation to a Property content type) — link listing photos directly to the property they belong to Why this matters The users-permissions User type extension is one of the most-used Strapi features precisely because real applications need more than the defaults. The same is true for media: in property management, e-commerce, and publishing, assets carry domain-specific metadata that belongs on the asset itself. The current workaround of a parallel shadow collection is fragile, harder to query, and invisible in the media library UI.

Strapi version: v5 --- What I'm asking for A set of image editing tools built directly into the media library admin UI, so content editors can manipulate and re-optimize images without leaving Strapi. Current behaviour The media library is view-only (except crop) after upload. Editing an image requires leaving the admin, using an external tool (Photoshop, Squoosh, GIMP), re-uploading, and re-linking the asset everywhere it is used. Re-optimization (reducing file size after the fact) is not possible at all from the admin. Expected behaviour An "Edit" button on any image asset opens an editing panel inside the admin Editing tools: crop (with aspect-ratio presets), resize, rotate, flip, basic adjustments (brightness, contrast) Re-optimization tool: re-run Strapi's image processing pipeline on an already-uploaded asset to regenerate formats at a different quality level or dimensions without re-uploading the original Saving a non-destructive edit creates a new derivative asset; the original file is always preserved Generated thumbnails and responsive formats are regenerated automatically after any edit Why this matters Content editors working in production — property managers, marketing teams — regularly need to adjust images post-upload. Today every adjustment is a multi-step round-trip outside the admin. Built-in tools keep the entire editorial workflow inside Strapi and remove the dependency on external software for routine tasks.

The Content Manager sidebar (list of collection types / single types) has a fixed width. Since the tree-like navigation for collection types was introduced, this became a real usability issue: each nesting level adds indentation, so items on the 3rd level get very little horizontal space. Most 3rd-level names are truncated to a few characters (e.g. "Acceleration…", "Directions F…", "Registrations f…"), so similar items can't be told apart without hovering or opening each one. It's even worse for non-English content: Cyrillic or German labels are often long and truncate faster. Meanwhile, on large monitors plenty of horizontal space stays unused. Proposed solution A draggable handle on the right edge of the sidebar to resize it with the mouse Reasonable min/max limits (e.g. 200px–480px) Persist the chosen width per user Double-click on the handle to reset to default width Why not alternatives Tooltips on hover are slow for everyday navigation, and reducing indentation doesn't scale with deeper trees. A resizable sidebar solves the problem for any nesting depth and any content language, without changing the default layout. Strapi version: 5.55.1

I would need a way to set alternativeTexts per language on files in the upload plugin. For now I just built a custom collection, which contains a file and localized alt text. However, I think this is a very common use case and related to i18n plugin, so I just opened as an issue. See: https://github.com/strapi/strapi/issues/10220

A global search that searches through all content types. Customers using the system have a lot of content and would like to be able to search through it all at once.

It would be really beneficial if there was a way to retain the order (using order column for example) of a collection and be able to update it via drag-and-drop on the collection view. There are many cases when we want to have a certain order of items (regardless of insert order/id/filter/sort options provided in the view), and to be able to retrieve the data using the predefined order later (as seen in the collection view for example) Using drag and drop would help as it's really tedious to go to a huge collection and pump the order column of each item (for a CMS user) or run a query on the database (for CMS power user) most common use case, ordering an employee list on a company website (or add a new employee at a specific position) see: https://github.com/strapi/strapi/issues/3946

In Strapi 5, the admin panel list views (for example, Content Manager entry lists) display dates using a fixed, non-configurable format. Dates are displayed as: Wednesday, February 4, 2026 at 3:24 PM Provide a supported way to configure the date and date-time format used in admin list views, for example: Global admin setting Locale-aware but overridable Support for common formats (ISO, short date, or custom pattern) Why this matters Improves readability for international teams Aligns the admin UI with organizational standards Datas take up so much space in the table layout Scope Admin panel only. No impact on stored data or APIs.