PricingSign inGet startedDashboard →

← Docs

Managing your site

SFTP file access

Every WordPress site can expose its files over SFTP for direct edits and uploads — enabled per environment, isolated, and locked down by default. Here's how it works and how to connect.

Belov Cloud gives you direct file access to your site over SFTP — secure file transfer tunneled through SSH. Each environment gets its own isolated account: live and staging are completely separate logins, so a staging credential can never touch production. The account is chrooted (locked) to that one environment's files — it can't see your other sites or the rest of the server — and it listens on a non-standard port, which cuts out most automated login attempts.

The SFTP tab on a site, with a per-environment Enable button and the connection details — host, port, and username
The SSH & SFTP tab — enable per environment, then copy the host, port, username, and one-time password.
  1. Open the SSH & SFTP tab and pick an environment
    On the site, go to SSH & SFTP and scroll to password SFTP. Live and staging each have their own toggle — enabling one has no effect on the other.
  2. Click Enable
    Belov Cloud creates an isolated account for that environment and shows you the connection details: host, the non-standard port, and username.
  3. Copy the password — it's shown once
    For security the password appears a single time, right after you enable. Save it to your password manager immediately, because it won't be shown again.
  4. Connect with any SFTP client
    Point a client like FileZilla, Cyberduck, or Transmit at the host and the exact port shown, using the username and one-time password. You'll land directly in your site's files.
  5. Repeat for staging if you need it
    Staging is a separate account with its own host, port, and password — enable it the same way when you want to edit the staging copy.
Need a shell?
This is password-based file transfer — handy in FileZilla, Cyberduck or Transmit. For a real command line with WP-CLI, rsync and VS Code Remote-SSH, use SSH with a key instead: every site has it, live and staging, in the same tab. For a safe place to test edits before they hit production, use the staging environment and push to live when it checks out.

Every WordPress site also has real SSH — WP-CLI ready, with rsync, a database tunnel and VS Code Remote-SSH.

SSH and WP-CLI →

← All guides