“Just upload the new brochure to the server.” If you run a small business or manage its office, you may have been handed that sentence with no further instructions, or been sent a host name and password by a designer and told to “use FTP”. Then three tool names appear at once: File Manager, FTP and SFTP. This guide is for the owner or office admin who needs to put a file on the website, replace one or let someone else do it, without breaking anything and without becoming a technician. It explains what the three ways of reaching your site’s files are, which suits which job, where a file must go to show up, what to do before you overwrite anything and how to give a designer access safely. Hosts set up their panels differently, so this is a method to adapt, not a promise about any one account.
Three ways to reach your site’s files
A website is a folder of files kept on a server: pages, images, style files and any documents you want visitors to download. To change the site you change those files. Hosting gives you a few doors to the same folder, and they all end up in the same place:
- File Manager. A tool inside your hosting control panel that you open in a browser. You see the folders and files, and can upload, download, rename, edit and delete. Nothing to install. What cPanel is and what an owner can do in it is covered in its own guide and not repeated here.
- FTP. File Transfer Protocol is an old standard way of copying files between your computer and the server using a separate program called an FTP client. It needs a host name, a username and a password. Plain FTP does not encrypt what it sends.
- SFTP. The same idea, normally used with the same kind of client program, but the connection is encrypted. It is the safer version of the same job. A related option some hosts offer is FTPS, which adds encryption to FTP in a different way.
Which doors your own plan opens is the host’s choice, so check your control panel and ask. Most cPanel accounts include a File Manager and an FTP accounts tool, but look in your own panel rather than assume.
Which one to use: a decision table
| Way in | Best for | Main risk |
|---|---|---|
| File Manager | One-off jobs: replace a single PDF, fix one file, download a copy, check a file’s date. Nothing to install. | Easy to delete or overwrite the wrong thing with one click. Slow and clumsy for hundreds of files. |
| FTP | Only where nothing else is offered, or on a network you fully control, for bulk uploads with an FTP client. | Plain FTP sends your username and password without encryption, so a login can be read by someone watching the connection. |
| SFTP | Bulk uploads, many files, regular updates by you or a designer, using an FTP client that supports it. | A login that is shared, kept too long or given too much access. The encryption protects the connection, not a careless password. |
A simple rule: for a handful of small edits use File Manager; for many files or regular updates use SFTP; treat plain FTP as the last resort. Uploading a whole site? Many File Managers let you upload one zip file and unpack it on the server, which is often easier than sending thousands of small files one by one. Check how yours does it.

FTP details in plain words, and why plain FTP is the weak one
A designer who “gives you FTP details” is giving you the few things an FTP or SFTP client needs to connect:
- Host: the address of the server to connect to.
- Username: the name of the FTP login. Many hosts let you create several, each separate from your main account login.
- Password: the password for that login.
- Port and protocol: a number and a choice (FTP, SFTP or FTPS) that the client needs. Use the exact values your host publishes, not a guess.
Your host’s welcome email or control panel shows the details for your account. Do not copy settings from a blog post or another website, because they differ between hosts. This guide does not give them.
The security difference is simple. Plain FTP sends everything, including the username and password, without encryption. On a shared or public network, such as café Wi-Fi, a person watching the connection could in principle read them. SFTP encrypts the connection, so what travels is scrambled. That is why the common advice is to prefer SFTP, or FTPS where only that is offered, and to avoid plain FTP when you have a choice. Whichever you use, a strong password that is unique to that login still matters, and so does turning on two-step verification on your main account where your host offers it.
Note that some control panels label every secure and insecure option “FTP accounts”. The label does not tell you the connection is encrypted. Ask which protocol the login supports.
Where an uploaded file must go
The most common reason an upload “did nothing” is that the file went to the wrong folder. A server holds many folders, and only one of them is the folder your website is served from. So before you upload anything, find your site’s main folder in File Manager first. Open it and look for the files you already know, such as your home page. On many cPanel accounts that folder is named public_html, but do not assume; look for the folder that holds your existing pages.
- Inside the main folder, the file is public. Anything you put there can be opened by anyone who knows or guesses its address. Never upload anything private, such as a staff list, a scan of an identity card or a customer spreadsheet.
- Outside the main folder, it does not show. A file in the wrong place is not broken, just not on the website.
- A subfolder becomes part of the address. A file called menu.pdf inside a folder called downloads appears at your site’s address followed by /downloads/menu.pdf. So you can plan where a link will point before you upload.
- Extra websites have their own folders. If one account holds more than one site or a subdomain, each usually has its own folder. Check which one belongs to the site you mean.
Made a change and cannot see it? First confirm the file is there and the date matches your edit. Why your site can look old after an update covers how to tell a file that never uploaded from one that is only cached.
Back up first, then name things carefully
Back up before you overwrite. Uploading a file with the same name as an existing one normally replaces it with no warning and no undo. So before you replace a page, a style file or a document, download the current version to your computer. For a bigger change, take a full backup of the site; the backup guide explains what to back up and how to test a restore. Do not keep an “old copy” in the public folder: anyone who guesses the address can open it, and it clutters the site.
Use safe file and folder names. Servers do not all treat names the way your laptop does. A few habits avoid most problems:
- Use lowercase letters, numbers and hyphens: price-list-2026.pdf, not Price List FINAL (2).pdf.
- No spaces. A space becomes a clumsy %20 in the address, and some tools break on it.
- Avoid accents, symbols and brackets. Keep the file ending, such as .pdf or .jpg, exactly as it is.
- Remember that many servers treat Brochure.pdf and brochure.pdf as different files, so link to the exact name.
Leave permissions alone unless told. Every file and folder has a permission setting that says who can read or change it. New uploads normally get a sensible setting automatically. Do not change it because a forum post suggests it, and above all do not make something “open to everyone” to make an error go away. A wrong setting can either break the page or leave a file open to anyone. If a designer or support asks you to change a permission, change that one item as asked and note it down.
Giving a designer access: a checklist
Designers and developers often need to upload files. You can allow it without handing over the keys to the whole account. (For the wider picture on account safety, see securing your cPanel account.)
- Make a separate login. Create a new FTP login for the designer in your control panel, with their own username and password. Never share your main control panel login.
- Give the least access that does the job. If your panel lets you restrict the login to one folder, do it, so a mistake or a stolen password reaches less.
- Use a strong, unique password. A long password you have never used elsewhere. Send the details through a channel you trust, not in a public group chat.
- Ask which protocol they will use, and prefer SFTP (or FTPS) over plain FTP.
- Agree the end date. The login exists for this job only.
- Remove it afterwards. When the job ends, delete the login. Some panels give a choice between deleting only the login and also deleting its files; for this purpose you want to remove the login, not your site’s files, so read the prompt carefully.
- Change passwords the designer saw. If they ever had a password to anything else, change it.
- Record who has access. Keep a short note: name, what they can reach, date given, date removed.
Disputes about who holds what are easier to avoid with this record. See who owns your website and, if a designer has gone silent with your logins, what to do when your web designer disappears.
Before you upload: a one-page checklist
- Be clear what you are changing and which page or address it affects.
- Open File Manager and find the main folder. Confirm it holds your existing pages.
- Find the current file and note its name, size and last-modified date.
- Download a copy of anything you are about to replace. For a big change, take a backup first.
- Check the new file’s name: lowercase, no spaces, correct ending.
- Check the new file’s content: the right version, no private information, a sensible size.
- Choose the method: File Manager for one or two files, SFTP for many.
- Upload to the correct folder, and watch for any “file exists” prompt before you confirm replacing it.
- Leave permissions alone.
- Open the live address in a private window or on your phone and check it.
- Write a one-line note: date, what changed, which method, who did it.
A made-up example: the PDF brochure
This example is made up to show the steps. The names and details are invented.
Mei Ling is the office administrator of a small trading company. Her manager asks her to replace the product brochure on the website with a new one by lunchtime. She has never touched the website files. Here is what she does.
- She logs in to the hosting control panel and opens File Manager. In the folder that holds the site’s pages she finds a folder called downloads, and inside it brochure.pdf with a last-modified date from last year.
- She downloads brochure.pdf to her computer and renames her copy brochure-old-backup.pdf. It stays on her computer, not on the server.
- The new file from the designer is called “Company Brochure FINAL v3.pdf”. She renames it on her own computer to brochure.pdf, so the existing link on the website keeps working, and checks that it holds the right version and nothing private.
- She opens the downloads folder in File Manager, uses Upload, and chooses the new file. File Manager warns that a file with that name exists; she confirms the replacement.
- The new brochure.pdf now shows today’s date. She opens the brochure link in a private window on her phone, and the new version appears.
- She notes in a shared file: “20 Nov, replaced downloads/brochure.pdf, File Manager, Mei Ling. Old version saved on office drive.”
Twenty minutes, one file, nothing else touched, and the old version can be put back in a minute if the manager spots a typo. Had the manager asked her to upload the whole redesigned site, or the designer had left, that would be a job for the designer or a developer, as the next section explains.
When to hand it to a developer, and what to do after a mistake
Hand it to a developer, or ask for help, when:
- You are replacing the whole site, moving it, or changing many files at once. (Testing first on a copy is explained in how a staging site works.)
- The files belong to a platform such as WordPress rather than being plain pages and documents, or you are asked to edit configuration or database files.
- You are asked to delete a folder, change permissions across many files, or edit a file you do not understand.
- A message appears that you cannot interpret, or the site shows an error after an upload.
If you make a mistake, in this order:
- Stop. Do not upload more files hoping to fix it. Each upload can add to the problem.
- Write down what you did: which file, which folder, roughly what time.
- Put the old copy back if you downloaded it. That fixes most single-file mistakes.
- Otherwise restore from a backup. Check first whether your host can restore one file or only the whole site, because restoring everything can remove other recent changes.
- Ask support, with the page address, what you changed, the time, and a screenshot of any error. Never send a password.
- Check from outside: a private window or another device, as above.
Common mistakes
- Uploading to the wrong folder, then concluding the upload failed.
- Replacing a file with no copy of the old one. There is usually no undo.
- Leaving “old” or “backup” files in the public folder, where anyone can open them.
- Uploading something private, such as a staff list, because it was handy.
- Using spaces, capitals and brackets in names, then wondering why the link breaks.
- Sharing the main control panel login instead of making a separate one.
- Never removing a designer’s login. It keeps working for years after they leave.
- Using plain FTP on public Wi-Fi.
- Changing permissions to make an error go away.
- Copying settings from another site’s instructions instead of the ones your host gave you.
Where Gotka Technologies fits
Gotka runs cPanel hosting on LiteSpeed web servers, and plans include daily backups, which are useful before and after any file change. Gotka also offers domain registration, and a web design service that runs from design through ongoing maintenance, which can suit owners who would rather not upload files themselves. New to the account? The first-week checklist shows where File Manager sits among the other first jobs.
This guide does not state which access methods Gotka plans offer, so treat these as questions, with answers unknown to this guide, to put to support in writing through the client-area ticket system, or by phone or WhatsApp on +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT). Your host’s welcome email or control panel shows the connection details for your account.
- Which methods does my plan support: File Manager, FTP, SFTP, FTPS?
- Where do I create a separate login for a designer, and can I limit it to one folder?
- Which host name, port and protocol should my designer use?
- Is there a limit on file size or on the number of files I can upload?
- Can a single file be restored from a backup, or only the whole site?
- How do I see which logins exist, and delete one safely?
Key terms used in this guide
- File Manager: a control-panel tool, used in a browser, for uploading, downloading, renaming, editing and deleting site files.
- FTP: File Transfer Protocol, a standard way to copy files between your computer and a server. Plain FTP is not encrypted.
- SFTP: a version of the same job over an encrypted connection.
- FTPS: FTP with encryption added in a different way, offered by some hosts.
- FTP client: the program on your computer that connects to the server to send and fetch files.
- Host, username, password: the three basic details a client needs to connect, plus a port and protocol.
- Main folder (document root): the folder the website is served from. Files outside it do not show on the site.
- Permissions: settings that say who may read, change or run a file or folder.
- Overwrite: replacing a file by uploading another with the same name.
- Backup: a saved copy of your files that you can restore from.
- Least access: giving a person only what they need for the job, and no more.
What is the difference between FTP, SFTP and File Manager?
File Manager is a tool inside your hosting control panel that works in a web browser, so nothing needs installing. FTP is a way of sending files between your computer and the server using separate software, and plain FTP does not encrypt what it sends. SFTP does the same job over an encrypted connection. File Manager suits small edits, while FTP or SFTP suits bulk uploads.
Is FTP safe to use for my website?
Plain FTP sends your username and password without encryption, so someone on the same network could in principle read them. SFTP encrypts the connection, and some hosts offer FTPS, which adds encryption to FTP. Use SFTP or FTPS where your host offers it, use a strong unique password, and ask your host which methods your plan supports.
Where should I upload a file so it shows on my website?
Into your site’s main public folder, or a folder inside it. On many cPanel accounts that folder is called public_html, but do not assume: open File Manager first and look at which folder holds your existing pages. A file placed outside that folder will not appear on the website, and a file inside a subfolder appears at an address that includes the subfolder’s name.
What should I do before I overwrite a file on my website?
Make a copy first. Download the current file to your computer, or take a backup of the site, so you can put the old one back. Do not leave an old copy in the public folder, because anyone who guesses the address can open it. Then upload the new file with the same name, check the page, and note the date and what you changed.
How should I give a web designer access to my website files?
Do not share your main control panel login. Create a separate FTP login for the designer, limit it to the folder they need if your panel allows, give it a strong unique password, and send the details through a channel you trust. When the job ends, delete that login, change any password the designer saw, and write down who had access and when.
Which file access methods does Gotka offer on its plans?
This guide does not say. Gotka lists cPanel hosting, so File Manager and FTP accounts are generic cPanel tools you can look for in your own panel, but it does not state whether SFTP, SSH, a particular limit or a specific setting is included on your plan. Ask support in writing through the client-area ticket system, or call or WhatsApp +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT).
Email Attachment Too Large? Why It Bounces and How to Send Big Files Without the Message Coming Back
Email attachment too large or bounced? Why size limits reject a message, how to read a message-too-large bounce, shrink files and send big files by link safely.
HostingYou Updated Your Website but Still See the Old Version? Browser, Server and DNS Caches in Plain Words
Website showing the old version after an update? Why browser, server and DNS caches cause it, the order to check, a quick test and when to open a ticket.
HostingContact Form Enquiries Not Reaching Your Inbox? The Usual Causes and How to Test
Customers say they sent your contact form but nothing arrives? Check spam, the recipient mailbox, outside tests, email authentication and plugins, step by step.


