Upload your website files
Which folder the files belong in, and the two mistakes that make a site look empty.
Updated 02 Sept 2026
A web server shows one particular folder to the world and ignores everything outside it. Getting files into that folder is the entire job.
The folder
On a লিনাক্স plan with সিপ্যানেল the folder is public_html. You will also see a www entry beside it — that is not a second folder, it is another name for the same one, so copying files into both achieves nothing.
On a উইন্ডোজ plan with প্লেস্ক the folder is httpdocs.
Getting the files there
The file manager inside the panel is the quickest route for a handful of files, and it will unpack a zip archive on the server, which beats uploading a thousand small files one at a time.
For anything larger, use an এফটিপি client. The panel creates the account; the host is your domain or the server name, and এসএফটিপি is worth choosing over plain এফটিপি wherever it is offered, because plain এফটিপি sends the password in the clear.
Two ways a correct upload still looks empty
The first is a folder too deep. Unzipping an archive often produces public_html/mysite/index.html, and the server looks for public_html/index.html. Move the contents up one level.
The second is the file name. The server serves index.html or index.php and nothing else by default — Index.html, home.html and default.html are all ignored, and on লিনাক্স the capital letter alone is enough to break it.
Where do I put a WordPress install?
The same folder — public_html, with wp-config.php sitting directly in it. Installing from the panel puts it there for you. Speeding up WordPress covers what to do once it is running.
Do file permissions matter?
Rarely, and mostly after an upload from a উইন্ডোজ machine. Folders want 755 and files 644; anything set to 777 is a security problem rather than a fix. The file manager can set these across a folder in one action.