By default, images and video are stored locally as data URLs. Connect a Cloudinary account so new uploads get a real hosted URL instead. This needs an unsigned upload preset from your own Cloudinary account — here's how to create one (Console → Settings → Upload → Upload presets → Add preset → Signing Mode: Unsigned).

Note: this only applies to new uploads going forward. Existing local assets aren't automatically migrated — you can re-drop a file to re-upload it. Pasting a Cloudinary (or any) URL directly into the Add box already works today regardless of this setting.

Push the file you're editing straight to a GitHub repo. This needs a fine-grained personal access token scoped to just this repo with Contents: Read & Write permission — nothing broader. The token is stored only in this browser's local storage; it never goes anywhere except directly to api.github.com.

Publish the file you're editing as a WordPress post via the REST API. Needs an Application Password (Users → Profile → Application Passwords in your WP admin) — not your real login password.

Back up the file you're editing to a Dropbox folder. Create an app at dropbox.com/developers/apps, then generate an access token for it under that app's settings.

Heads up: browsers can't open raw SFTP/SSH connections — that's a hard security limit, not a bug. This panel saves connection profiles for your reference (host, port, remote path), but actually transferring files needs a small backend to relay the connection. It won't upload/download on its own.

Pick an entire folder and every HTML/CSS/JS file inside it (including subfolders) gets scanned and queued for import.