Skip to main content
Add Studio to the panels where your team works. The Filament adapter uses your application’s Studio workspaces, storage and access policies.

Pick existing media

Save a pinned cover image, document or ordered gallery.

Upload to Studio

Send native Filament uploads to a workspace or folder.

Insert media into an editor

Connect RichEditor, MarkdownEditor or FLEX Rich Editor.

Display media on records

Render Studio thumbnails in an Infolist or table column.

Add Filament actions

Choose, download, move, rename, trash and restore files.

Configure panel access

Use Spatie with optional Guardian or Shield support.

Setup

Follow the panel setup guide to deploy the browser build and verify a complete form. The PHP configuration reference lists the Studio-specific options and defaults for each component.
  1. Install the Studio Laravel package and migrations in the host application. Register the panel’s user model in Studio’s principal map.
  2. Create Studio permission definitions for the panel’s authentication guard and assign the appropriate permissions. Give the user access to the workspace used by the component.
  3. Publish the matching Studio browser distribution. Use its standalone studio.js, studio.css and studio-mark.svg, and serve rich-editor-extension.js beside studio.js when integrating RichEditor. Point each field at the module and stylesheet URLs served by your application.
  4. On a tenant panel, register TenantStudioPlugin so picker requests, thumbnails and file delivery keep the authenticated tenant context.
The component examples use application-owned workspace and folder ULIDs and published asset URLs. Resolve IDs from the current authorized record, user or tenant. Studio handles media access and version resolution alongside your host model’s Filament policies.

Choose a component

Use native FileUpload

Use Filament’s FileUpload when your application owns the saved file. The disk and directory below are Laravel storage settings. The destination is the campaigns/covers prefix on the s3 disk.
To display the saved original and its conversions in Studio, configure an application media source. Have the owning model register the stored path and metadata when the record is saved. Register each conversion when your processing job completes. Studio shows the registered media in App assets, where the owning application retains control of file replacement and deletion. If you already use Spatie Media Library, let Spatie own the upload and its conversions. Mount the collection and choose which ready conversions Studio should use for thumbnails and previews. Spatie is optional for the native FileUpload example above.

Upload directly into a Studio workspace

Use StudioFileUpload for a native FileUpload field backed by Studio. Configure the workspace, the upload folder, the accepted MIME types and whether the field can select existing assets. Studio uses the workspace’s storage and processing settings, including S3 where configured.