iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
To edit a live homepage with FileZilla, connect to your server, open the site’s document root in the Remote site pane, right-click index.html, choose View/Edit, change the downloaded copy in a text editor, save it, and approve FileZilla’s upload prompt. FileZilla transfers the file; your text editor makes the HTML changes.
What FileZilla actually does when you edit index.html
FileZilla Client is primarily a file-transfer program. Its View/Edit command does not open the remote file as a live, directly editable document. Instead, FileZilla downloads a temporary local copy, opens that copy with the editor associated with the file type, and watches for a saved change. After you save, FileZilla can ask whether to upload the modified copy back to the server.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute
That distinction explains the most common surprise: saving in the editor does not necessarily publish anything until the upload completes. The practical sequence is always download, edit locally, upload, then verify the live page.
What you need before connecting
- The server host name or IP address supplied by your hosting provider.
- Your FTP, FTPS, or SFTP user name.
- Your password, private-key configuration, or other authentication method required by the provider.
- The protocol and port specified by the provider. Standard defaults are FTP/FTPS on port 21 and SFTP on port 22, but the provider’s settings take precedence.
- Permission to write to the website’s document root and to replace its
index.html. - A plain-text or code editor. A word processor that inserts formatting is not appropriate for HTML.
If you do not have server credentials or a web-hosting account, FileZilla alone cannot change a public website. It is a client for an existing FTP-family or SFTP service.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Choose the safest connection method available
Ask the provider which protocol it supports and use the most secure supported option. Plain FTP sends the session without encryption. FTPS adds TLS protection, while SFTP runs through an encrypted SSH connection.
| Protocol | Encryption | Typical default port | When to use it |
|---|---|---|---|
| FTP | None; commands and data are unencrypted | 21 | Only when the provider offers no encrypted alternative and the risk is understood |
| FTPS | TLS encryption | 21 is common, but the provider may require another port | When the provider supplies an FTP-over-TLS endpoint and certificate settings |
| SFTP | Encrypted through SSH | 22 | Preferable when available, especially on untrusted networks |
Do not change a port merely because it is common. A provider can assign a nonstandard port, and using the wrong one produces a connection failure even when the host name and password are correct.
Connect to the server in FileZilla
- Open FileZilla Client.
- Enter the host, user name, password or key details, protocol, and port provided by your host. You can use the quick-connect fields for a one-off session or save a complete entry in the Site Manager.
- Start the connection and read the message log for authentication or certificate prompts. Accept a certificate only when it matches the provider’s instructions.
- Wait until the Remote site pane displays directories and files. If that pane is empty, the login may have succeeded while the requested directory failed to load; check the status messages before proceeding.
Keep the Local site pane visible as well. FileZilla will place a View/Edit download in a local temporary location, but knowing where your own backup folder is makes manual recovery easier.
Find the website’s document root
The document root is the remote directory whose contents are served as your website. Its name depends on the hosting account. public_html is a common example, but it is not universal; a provider may document another directory. Do not assume that the first directory shown after login is the web root.
How to identify the right directory
- Use the directory name and path in your provider’s setup instructions.
- Look for the existing homepage, other public assets, and directories used by the site. Their presence is a clue, not proof; confirm the path with the provider’s documentation.
- If several domains or subdomains share the account, each may have a different document root. Select the one belonging to the site you intend to change.
- Record the complete remote path before editing. You will need the same path if you perform a manual upload or rollback.
Editing an identically named file in a private, staging, or unrelated directory can succeed technically while leaving the public homepage unchanged.
Back up index.html before touching it
In the Remote site pane, select the current index.html and download it to a dated backup folder on your computer. Keep the original filename and note the remote directory. A second precaution is to make a duplicate such as index.html.backup-2026-10-14 locally; do not upload that duplicate unless you deliberately want it publicly accessible.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Download the file even if you plan to use View/Edit. The temporary copy used by FileZilla is convenient for a quick change, but a separate backup is easier to find after you close the session. Never overwrite your only known-good copy before the new page has been checked.
Set a text editor for View/Edit
If View/Edit launches a browser or another unsuitable application, fix the file association before editing. In FileZilla, open Edit > Settings > File editing. Depending on the version, select the system default editor or choose Use custom editor and browse to the executable for your preferred code or text editor.
The goal is an editor that preserves plain text and lets you see HTML tags. A browser is useful for previewing a finished page, but it cannot safely replace an HTML source editor in this workflow.
System default versus custom editor
| Choice | Best for | What to check |
|---|---|---|
| Use system default editor | Computers where .html is already associated with a suitable code editor |
Confirm that the operating system does not route HTML files to a browser |
| Use custom editor | Reliable, repeatable editing on a shared or newly configured computer | Browse to the actual editor executable, not a document or shortcut that cannot accept a file |
FileZilla Pro also documents file-type associations. In an association command, %f represents the file path passed to the editor. Use that syntax only in the association mechanism that your installed edition exposes.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →FileZilla’s documented instruction is: “To be prompted to upload an edited file, first enable the Watch locally edited files and prompt to upload modifications option.” Turn on Watch locally edited files and prompt to upload modifications in the file-editing settings if it is not already enabled.
Edit index.html without damaging the page
- In the Remote site pane, open the confirmed document-root directory.
- Right-click the live
index.html. - Choose View/Edit (some versions show Edit).
- Wait for FileZilla to download the temporary local copy and open it in the configured editor.
- Make a small, deliberate change. Preserve the existing document structure unless you understand the consequences of changing it.
- Save as plain text, retaining the exact filename and an HTML extension. Do not use “Save as” to add a second extension such as
.html.txt.
For a simple test, you might change the text inside an existing heading:
<h1>Welcome to our site</h1>Change only the text between the tags:
<h1>Welcome to the new homepage</h1>Keep quotation marks around attribute values, close elements correctly, and avoid pasting styled content directly from a word processor. If you are adding a link, verify both the opening and closing tags:
<a href='about.html'>About us</a>When replacing larger sections, copy the original into a separate local file first. That gives you a clean comparison point if the new markup produces an unexpected result.
Recommended Free Tools
Save and upload the modified file
Automatic upload prompt
After saving the local copy, return focus to FileZilla or close the editor. With file watching enabled, FileZilla detects the changed timestamp and asks whether to upload the modification. Choose the upload option, confirm the destination if prompted, and watch the transfer queue until the item is listed as successful.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
The prompt is an upload decision, not a confirmation that the public page has rendered correctly. A completed transfer means the bytes reached the selected remote path; browser verification is still required.
Manual Transfer when no prompt appears
If FileZilla does not ask to upload, use its explicit transfer command:
- Leave the edited file saved in the local temporary location, or save a copy in a known local folder.
- In FileZilla, open Transfer > Manual Transfer.
- Choose Upload.
- Select the local
index.htmlfile. - Enter or browse to the exact remote document-root path containing the original file.
- Start the transfer and resolve any overwrite confirmation in favor of replacement only after checking the local file and destination.
- Wait for the queue and status area to report completion.
Another straightforward method is to select the saved local file in the Local site pane and drag it to the matching directory in the Remote site pane. Confirm the destination carefully; a drag to the wrong directory can upload successfully without changing the page visitors see.
Verify that the new homepage is live
- Wait for FileZilla’s queue to show that the transfer completed rather than failed or remaining queued.
- Open the site’s homepage in a browser using the intended domain.
- Refresh the page. If the old content remains, perform a hard refresh or test in a private window to rule out a cached response.
- Use the browser’s “view source” feature to see whether the changed text is present in the HTML returned by the server.
- Open the browser developer tools and inspect the console if the page is blank, partially rendered, or reporting failed resources.
- If the source still contains the old text, return to FileZilla and verify the remote directory, filename case, and transfer result.
Filename case matters on many servers. A request for index.html is not necessarily the same as a file named Index.html. Preserve the existing spelling unless you are intentionally changing the site’s references.
Troubleshoot the problems people hit most often
View/Edit opens Chrome, Edge, Safari, or another browser
HTML files are often associated with a browser by default. Go to Edit > Settings > File editing, select a system association that points to a text editor, or choose Use custom editor and browse to the editor executable. Then retry View/Edit. Opening the file in a browser does not provide a safe source-editing workflow.
There is no upload prompt after saving
First, enable Watch locally edited files and prompt to upload modifications. If the prompt still does not appear, use Transfer > Manual Transfer and upload the saved local copy to the original remote path. Confirm that the editor actually saved the temporary file rather than a new file in another directory.
The homepage does not change
- Check that the transfer queue reports success.
- Confirm that you uploaded to the site’s actual document root, not a similarly named folder, staging area, or another domain’s directory.
- Check the exact case and spelling of
index.html. - View the page source to distinguish an old server response from a browser rendering problem.
- Refresh without using the browser’s cached copy.
The connection fails before the files appear
Recheck the host, protocol, port, user name, password, and authorization with the provider. Port 21 is a standard FTP default and port 22 is a standard SFTP default, but neither is guaranteed. A provider may require FTPS, an SSH key, a particular encryption mode, or a nonstandard port. An incorrect protocol can look like a bad password, so compare every field with the provider’s connection instructions.
Free tools Windows power users keep installed
One-click scans. No signup required.
Permission is denied during upload
A successful login does not guarantee write permission. Confirm that the account is allowed to modify the document root and that you are not attempting to replace a file owned by another account or located outside your assigned web space. If the provider manages permissions, ask for the correct writable path rather than repeatedly retrying the transfer.
The page becomes blank or displays broken markup
Use your local backup to compare the changed section with the original. Look for an unclosed quote, a missing closing tag, or text inserted outside the document structure. Restore the known-good backup if visitors are affected, then reapply the change in a smaller step. Uploading a syntactically valid file does not guarantee that the browser will render every element as intended.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Decide which editing workflow fits the change
| Workflow | Advantages | Risks and controls |
|---|---|---|
| View/Edit with automatic watching | Fast for a small change; FileZilla notices a save and offers the upload | Easy to forget that the temporary file still needs approval; keep the backup and check the queue |
| Download, edit in a known folder, then Manual Transfer | Clear local history and easier comparison before publishing | More opportunity to select the wrong remote path; record the original directory |
| Download a backup only, then edit the remote file through View/Edit | Minimal setup for a one-line change | Rollback depends on finding the backup; do not skip the download |
For a one-off headline or contact-detail update, View/Edit is usually the shortest route. For a substantial redesign, keep a complete local project copy and make a deliberate upload rather than relying on a temporary file.
A repeatable safe-edit checklist
- Confirm the website, document root, and remote filename.
- Confirm that the connection uses the provider’s intended protocol; prefer encrypted SFTP or FTPS when available.
- Download and label a backup of the current
index.html. - Use a plain-text editor configured under Edit > Settings > File editing.
- Make the smallest change that solves the problem.
- Save the local file and verify the filename and extension.
- Accept the automatic upload prompt or perform a Manual Transfer upload.
- Wait for a successful queue result.
- Refresh the live page and inspect source or console output if the result is not visible.
- Keep the backup until the page has been checked and the change is known to be correct.
How to roll back a bad change
Stop making additional edits if the new page is broken. In FileZilla, select the saved backup in your Local site pane, start a Manual Transfer upload, and target the exact remote directory that contained the original file. Confirm the overwrite, wait for the queue to finish, and reload the site. If the backup was downloaded before the edit, it represents the last known-good version; if it was not, ask the provider whether server backups or a hosting control-panel restore is available.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat FileZilla cannot solve for you
FileZilla can authenticate, transfer files, and hand them to an external editor. It cannot determine which of several directories is the correct web root, repair invalid HTML automatically, resolve application-generated homepages, or guarantee that a browser will display a changed page when a cache or server-side system is involved. Those decisions require the hosting provider’s path information and your site’s own structure.
Once you treat View/Edit as a download-edit-upload workflow, the process is predictable: secure connection, confirmed document root, backup, controlled local edit, completed transfer, and browser verification.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
