Skip to main content
Both upload adapters support the same Studio configuration. Call studio() with a server-resolved workspace ULID (or closure), the module URL, and optionally the stylesheet URL, uploadFolder, acceptedMimeTypes, allowLibrarySelection and generateRenditions. The default destination is the configured scope root, or the workspace root when no scope is set. Direct upload, library selection and rendition processing are enabled initially. The native adapter publishes on form save, while the FLEX adapter publishes immediately by default. Workspace and folder closures use current field context and Filament utility injection. Supply application-owned workspace IDs for the authenticated tenant. Studio rechecks workspace access on selection, validation, metadata resolution and publication. Folder checks use the current server hierarchy. Configure S3-compatible disks, encryption and renditions in Studio’s storage and processing settings. FileUpload’s native disk() and directory() configure its native transport. Studio folder IDs determine the logical Studio destination. Existing Spatie collections can be exposed through the optional Studio Spatie source adapter, retaining their existing storage/conversion ownership. FLEX assets use its existing per-instance asset manager. Studio’s React module and stylesheet load when the picker modal mounts. Closing the modal disposes its React instance. Each instance retains its own scope, state and lifecycle. Register media usages when saving the application record. Removing a form reference keeps the workspace asset under Studio’s normal ownership and retention policy.

Choose a thumbnail per record

This example uses a persisted Campaign. For create forms, resolve the workspace from authenticated context so the field can render before the record exists. See media references for deletion and validation.