Enable the server integration
From the Laravel host, publish the optional extension migration and run migrations.Prepare the account
Studio also requires write access to the destination workspace. Install the package’s permission definitions and assign the needed abilities through your existing roles. Permissions and roles
Download a ready-built extension
SHA-256 checksums are provided alongside the ZIPs. Firefox temporary installations are removed when Firefox restarts. A signed permanent Firefox add-on and store-installed Chrome version require separate store publication; these downloads do not claim to be store versions.
Build from source (optional)
With the checkout’s dependencies installed, build the extension from the repository root.
Pin the extension icon if you want quick access to its popup. After rebuilding, reload the installed extension in the browser’s extension manager and refresh source pages where it was already active.
Install for Chrome
In Chrome 120 or later, loaddist/chrome through chrome://extensions → Developer mode → Load unpacked. Pin FLEX Capture in the browser toolbar, then follow workspace approval below.
Install for Firefox
In Firefox 140 or later, selectdist/firefox/manifest.json through about:debugging → This Firefox → Load Temporary Add-on. Reload the temporary extension after a browser restart, then approve its workspace below.
Approve a workspace
- Open the extension popup, then Preferences → Websites and connections → Connect Studio. A disconnected save surface also directs you to this popup.
- Enter the installation address. Grant the browser access to that Studio host when requested.
- The extension opens Studio’s approval page. Sign in with your normal Studio account.
- Compare the eight-character code in Studio with the extension’s code, choose the destination workspace and approve it.
- Return to the popup and confirm the connection has completed. In Batch save, check the destination and save one allowed test file.
Discovery and custom paths
When given an installation URL, the extension discovers the API through/.well-known/flex-media-studio.json on that origin. The returned approval URL and API base must stay on that origin.
If discovery is unavailable, the current client can accept the complete extension endpoint when its path ends in /extension/v1. For example, https://studio.example.com/media-studio/extension/v1. With a customized endpoint suffix, keep well-known discovery reachable. Production hosts use HTTPS. Localhost, loopback and .test development hosts can use HTTP.
Connect another workspace or revoke a device
Repeat Connect Studio and approve the additional workspace. The save surface can then offer those connections when workspace switching is enabled. An existing approval does not automatically grant access to another workspace. Use the browser integration in Studio to review and revoke your connected devices. Revocation blocks subsequent authorized requests. Expired or revoked connections need a new approval. A maximum of 20 active devices per principal and workspace is enforced.Resolve installation problems
For files behind a website login, review Download through the browser.