Edit and save server files over SFTP on iPhone

Before you start

• An SFTP server you are authorized to access, an account, and its password or private key.
• Network access to the server, with read and write permission for the target file.
• The expected SSH host fingerprint from your administrator before the first connection.

Step by step

1. Create an SFTP connection

   Open the server connection entry point, select SFTP, and enter the address, port, remote path, and username. Use the configured port; 22 is common but is not guaranteed.

2. Configure authentication and verify identity

   Select password or private-key authentication as configured by the server. Verify a new SSH host fingerprint against an independent value from the administrator before trusting it. Recheck unexpected fingerprint changes.

3. Test and save the connection

   Run Test Connection and save after it passes. A successful connection test does not imply write access to every directory.

4. Open a file for remote editing

   Browse the server and use remote editing for supported text, Markdown, code, or configuration files. Importing into the internal file space instead creates a local copy that does not automatically write back.

5. Save and verify on the server

   Choose Save, wait for success, and reopen the same remote path to check the result. If another process has changed the file, review or save a separate copy before deciding whether to overwrite.

Protocol   SFTP
Server     example.com
Port       22 (use the configured port)
Path       /home/example/documents
Auth       Password or private key

Scope and limitations

• Remote editing and saving need connectivity and depend on server permissions, storage quotas, and connection state.
• WebDAV and FTP currently support read-only browsing and importing; they do not provide the same direct save-back flow as SFTP.
• The text editor can edit code but does not compile or run it. Running commands belongs to the separate SSH terminal feature.

Troubleshooting

The connection test fails

Check connectivity, address, port, firewall, authentication, and whether the account can access the remote path.

Reading works but saving fails

Check write permissions, available server storage, and connection state. Keep a local copy and verify the server before retrying.

The server file did not change

Confirm you opened a remote editing session rather than an imported copy. Look for a successful save, then reopen the same remote path.

Common questions

Does FTP save back in the same way?

No. PatchDoc supports SFTP save-back; WebDAV and FTP currently focus on read-only browsing and importing.

Will offline edits automatically synchronize?

Do not treat remote editing as offline automatic synchronization. A remote save needs an active connection and should be checked on the server afterward.