With the cPanel File Manager you can upload, download, and edit files directly via your browser to your web hosting. For individual files or minor changes, you therefore do not need an additional FTP program.
In this guide, we will show you step by step how to upload, download, and edit files in the CURIAWEB cPanel using the integrated editor. You will also learn what to look out for when overwriting existing files and how to secure your changes.
Important: Changes in the file manager directly affect the files of your hosting account. For files of an active website, changes can therefore become visible immediately or affect the functionality of the website.
1. Open file manager #
Log in to your CURIAWEB cPanel.
Then open:
Files → File Manager
If you are not yet familiar with the setup and directory structure, read first Use cPanel File Manager.
2. Open the correct destination directory #
Before you upload or edit a file, you must open the correct directory.
For the main website, the document root in a typical cPanel configuration is often located at:
public_html
However, for additional domains or subdomains, a different document root can be used.
Attention: Do not just upload files to
public_html, just because this folder exists. If there are multiple websites, first check which directory actually belongs to the desired domain.
3. Upload file to web hosting #
Open the folder in the file manager where the file should be saved.
Then click on Upload.
Select the desired file on your computer or drag it—if the interface supports this—into the designated upload area.
cPanel then starts the transfer.
4. Allow the upload to complete fully #
Wait until the upload is completely finished.
Do not leave the upload page prematurely and do not close the browser window during an ongoing transfer.
After a successful upload, you can return to the file manager.
5. Check uploaded file #
Then check whether the file appears in the desired directory.
Check in particular:
- Filename
- file extension
- File size
- Destination directory
For example, if you:
logo.webp
you wanted to upload, but in the file manager:
logo.webp.txt
appears, the file extension is incorrect.
Pay attention to file extensions #
The file extension often indicates what type of file it is.
Typical examples are:
.html
.php
.css
.js
.jpg
.png
.webp
.pdf
Do not change a file extension arbitrarily. Renaming bild.jpg in bild.webp does not convert the actual image format, for example.
Briefly explained: Renaming a file extension is not file conversion. The content of the file remains unchanged.
6. Do not accidentally overwrite existing file during upload #
Special care is required if a file with the same name already exists in the target directory.
For example:
style.css
or:
index.php
If an existing file is replaced by a new version, the previous content may be lost.
This can have an immediate impact on the website.
Back up existing file beforehand #
If you want to replace an existing file, download the previous version to your computer beforehand or create a clearly labeled backup copy.
For example:
style.css
can you temporarily act as:
style-backup.css
secure.
Important: Such a file copy is merely a short-term safeguard for this individual file and does not replace a complete website backup.
7. Download file #
To back up a file on your computer, open the corresponding directory in the file manager.
Select the desired file and choose Download.
Your browser will then download the file to your computer.
Check after the download whether the file was actually saved.
When is downloading before editing useful? #
For important files, you should always keep an unmodified version before making any changes.
This particularly affects configuration and program files such as:
.htaccess
wp-config.php
functions.php
or individually customized PHP, CSS and JavaScript files.
If a change fails, you can upload the previous version again.
8. Download multiple files #
If you want to download multiple files or an entire folder, it is often more practical to first combine the data into an archive.
Instead of downloading hundreds of individual files, you can, for example, create a ZIP archive and then transfer just that single file.
We show how this works at Compress and extract ZIP files in cPanel.
Consider large downloads #
With very large files or extensive websites, working via the browser can be less convenient.
For regular or extensive file transfers, an FTP connection may be more suitable.
We handle the setup under Create an FTP account in cPanel.
9. Edit file directly in cPanel Editor #
You can edit text-based files directly in the file manager.
Highlight the desired file and select the function Edit or rather the available editor.
cPanel then opens the file content in the browser.
Depending on the file type, the editor can be used, for example, for the following files:
.txt
.html
.css
.js
.php
and various configuration files.
10. Check character encoding #
When opening a text file, cPanel may ask for the character encoding or detect an encoding, depending on the interface.
Modern websites often UTF-8 used.
If a file is already working correctly, you should not change its encoding without a reason.
Incorrect character encoding can cause umlauts or special characters to be displayed incorrectly, for example.
From:
Greetings from Chur
faulty encoding could result in a display with unexpected characters.
Practical Tip: If you only want to change a single line in an existing file, keep its existing character encoding.
11. Carry out desired change #
Make only the necessary change in the editor.
For example, if you want to change a value, edit only the relevant part if possible.
Avoid making multiple independent changes at the same time.
This makes it much easier to determine later on which change caused an error.
Save file #
Check the change again and then save the file.
The saved version will then be located directly on the server.
For an active website, the change can take effect immediately.
Important: The cPanel editor does not have the same security logic as a content management system. If you save a faulty PHP or configuration file, the error can appear immediately on the website.
13. Test website immediately #
After making a change, open the affected website or function in a second browser tab.
Check if everything continues to work as expected.
For example, with a CSS change you control the presentation, with a PHP change you check the affected function, and with a configuration change you check the accessibility of the website.
Do not wait until the next day to review a change.
Consider browser cache for visible changes #
For example, if you have modified a CSS or JavaScript file, your browser may still use an older cached version.
If a change appears not to be visible, this does not automatically mean that the file was not saved.
If necessary, check the browser cache or existing website caches before making the same change multiple times.
Undo change #
If the website no longer works correctly immediately after your change, restore the previous state if possible.
If you downloaded the original file beforehand, you can upload it again.
Alternatively, you can rename or copy back a previously created backup.
Basic rule: If an error occurs immediately after a file modification, check that exact modification first before changing any other settings.
Edit PHP files #
Special care is required with PHP files.
A missing character, a misplaced parenthesis, or another syntax error can cause the file to no longer execute.
In the case of a central PHP file, this can affect the entire website.
Do not unnecessarily modify WordPress files directly #
In WordPress, you should normally not edit core files manually.
This includes in particular files within:
wp-admin
and
wp-includes
Such changes can be overwritten during a WordPress update and corrupt the installation.
Also edit theme files with care #
Direct changes to a WordPress theme can also be overwritten during a later theme update.
Depending on the task, a child theme or a designated configuration option, for example, is more sensible for permanent individual customizations.
.Edit .htaccess #
The file .htaccess is particularly sensitive, because even a single faulty instruction can impair the accessibility of a website.
Therefore, always create a backup before making any changes to it.
We cover how to work safely with this file in detail at .htaccess explained and safely edited.
.htaccess is not visible #
If you .htaccess can't find in the file manager, the file may simply be hidden.
Files whose names begin with a period are treated as hidden files on Linux systems.
We show how to fade them in under Show hidden files like .htaccess in cPanel.
Edit wp-config.php #
The WordPress file:
wp-config.php
contains important installation settings and may contain sensitive data, among other things.
Only change them if you know exactly which setting needs to be adjusted.
Create a backup beforehand and do not publish the contents of this file in forums, screenshots, or publicly accessible documents.
Safety: Configuration files may contain credentials or other confidential information. Do not share their full content publicly.
Edit CSS files #
In the case of a CSS file, errors usually do not lead to the complete failure of the website, but they can alter the appearance.
For example, if you change a color, font size, or spacing directly in the stylesheet, test the website afterwards on the affected pages.
For responsive websites, you should also check the display on different screen sizes if necessary.
Edit JavaScript files #
An error in a JavaScript file can impair the interactive functions of a website.
This can affect menus, forms, sliders or other dynamic elements, for example.
Therefore, after making changes, test not only whether the page loads, but also the specific function affected.
Edit HTML files #
For static HTML files, you can modify content directly in the editor.
Make sure to open and close HTML tags correctly.
Faulty HTML structure can affect the rendering of the page, even if the file remains accessible.
File is not displayed on the website after upload #
If an uploaded file does not appear where you expect it to, check the storage location first.
Typical causes are:
- wrong destination directory
- wrong document base
- different filename
- wrong file extension
- Capitalization
- cached website or browser content
Pay attention to upper and lower case letters #
On Linux-based web servers, file names are fundamentally case-sensitive.
The files:
Logo.webp
and
logo.webp
can therefore be two different files.
If your HTML code:
logo.webp
calls, but the uploaded file:
Logo.webp
meaning this can lead to an error.
Practical Tip: Use consistent lowercase for web files whenever possible. This reduces avoidable problems with file paths.
Avoid spaces in file names #
Spaces in web file names are technically possible, but can lead to unnecessarily complicated URLs and sources of error.
Instead:
My New Brochure.pdf
is for example:
meine-neue-broschuere.pdf
clearer.
Upload is not working #
If a file cannot be uploaded, check first:
- whether sufficient storage space is available
- whether you are working in the correct directory
- whether the transmission has been completely finished
- whether the file name and file size are plausible
- whether a specific error message is displayed
You should record an error message as completely as possible before making any further changes.
Large file cannot be uploaded #
For very large files, technical limits or browser-based transfer can play a role.
If you regularly need to transfer large amounts of data, the file manager is not always the best method.
In such cases, an FTP connection may be more appropriate.
File cannot be saved #
If the editor cannot save a file, permissions or other technical limitations, among other things, may play a role.
Do not change the file permissions immediately to the highest possible value.
First, check the existing permissions and the specific error message.
We explain how file permissions work at How to correctly set file permissions 644 and 755 in cPanel.
Why 777 is not a standard solution #
When dealing with write permission issues, the internet often recommends setting files or directories to:
777
to set.
This is not a sensible blanket troubleshooting method and can grant unnecessarily far-reaching access rights.
Determine the actual cause instead.
Website shows error 500 after editing #
If right after editing a PHP or .htaccess-File in 500 Internal Server Error appears, first restore the previous file version.
If the error disappears with that, the cause was very likely the change that was made.
We cover a detailed diagnosis under Fixing a 500 Internal Server Error.
File accidentally overwritten #
If you have accidentally replaced an existing file with a new version, first check whether you previously created a local copy or a backup.
If such a version is available, you can upload it again.
If you are missing your own backup, you should not try to reconstruct the original content from memory if it is an important file.
Check instead whether a suitable backup or recovery option is available.
File accidentally deleted #
Wenn eine Datei gelöscht wurde, kontrolliere zuerst den Papierkorb des Dateimanagers, sofern dieser beim Löschen nicht umgangen wurde.
Ist die Datei dort noch vorhanden, kannst du sie wiederherstellen.
Wie Löschen und Papierkorb grundsätzlich funktionieren, erklären wir im Grundlagenartikel zum cPanel-Dateimanager.
Sensible Dateien nicht öffentlich hochladen #
Bevor du eine Datei in ein öffentlich erreichbares Verzeichnis hochlädst, solltest du überlegen, ob deren Inhalt über das Internet zugänglich sein darf.
Particularly critical are, for example:
datenbank-backup.sql
passwoerter.txt
kunden.csv
website-backup.zip
Solche Dateien gehören nicht ungeschützt in einen öffentlich erreichbaren Dokumentenstamm.
Temporäre Dateien nach der Arbeit entfernen #
Wenn du eine Datei nur vorübergehend für Wartungsarbeiten hochgeladen hast, entferne sie nach Abschluss der Arbeiten wieder, sofern sie nicht mehr benötigt wird.
This applies in particular to:
- Backups
- SQL-Dateien
- Testdateien
- Installationsdateien
- temporäre Archive
So reduzierst du unnötigen Speicherverbrauch und vermeidest, dass sensible oder veraltete Dateien dauerhaft erreichbar bleiben.
Keine unbekannten Dateien aus dem Internet hochladen #
Lade keine PHP-Skripte oder anderen ausführbaren Dateien aus unbekannten Quellen auf dein Hosting, nur weil sie angeblich eine bestimmte Funktion bereitstellen oder einen Fehler reparieren.
Eine solche Datei kann schädlichen Code enthalten und Zugriff auf Website-Daten oder den Hosting-Account ermöglichen.
Safety: Prüfe Herkunft und Zweck einer ausführbaren Datei, bevor du sie auf den Server hochlädst. Bei unbekanntem Code ist Vorsicht wichtiger als eine schnelle Problemlösung.
Dateimanager oder FTP für Änderungen? #
Für eine einzelne Konfigurationsdatei oder einen kleinen Upload ist der Dateimanager meist sehr praktisch.
Bei umfangreichen Website-Dateien, regelmäßigen Übertragungen oder vielen Verzeichnissen kann ein FTP-Programm übersichtlicher sein.
Beide Methoden greifen letztlich auf Dateien deines Hosting-Accounts zu. Eine falsche Änderung wird deshalb nicht dadurch sicherer, dass sie per FTP statt über den Dateimanager durchgeführt wird.
Empfohlener Ablauf beim Ersetzen einer Website-Datei #
- Öffne den richtigen Dokumentenstamm.
- Suche die vorhandene Datei.
- Lade die bisherige Version als Sicherung herunter.
- Kontrolliere Namen und Dateiendung der neuen Datei.
- Lade die neue Version hoch beziehungsweise ersetze die Datei bewusst.
- Prüfe, ob Upload und Dateigröße plausibel sind.
- Teste die Website unmittelbar.
- Stelle bei einem Fehler die vorherige Version wieder her.
Empfohlener Ablauf beim Bearbeiten einer Datei #
- Öffne die richtige Datei im richtigen Verzeichnis.
- Erstelle vor der Änderung eine Sicherung.
- Öffne die Datei im Editor.
- Behalte die bestehende Zeichencodierung bei.
- Ändere nur die notwendige Stelle.
- Kontrolliere die Änderung.
- Speichere die Datei.
- Teste die Website beziehungsweise Funktion sofort.
Basic rule: Sichere zuerst, ändere gezielt und teste sofort. Mit diesem einfachen Ablauf lassen sich viele Probleme bei direkten Dateiänderungen vermeiden.
When should you contact support? #
Wenn ein Upload oder eine Bearbeitung nicht funktioniert und die Ursache unklar ist, notiere möglichst die konkrete Fehlermeldung.
Für eine Analyse sind insbesondere folgende Informationen hilfreich:
- affected domain
- Filename
- Verzeichnis beziehungsweise Pfad
- gewünschte Aktion
- ungefähre Dateigröße bei Uploadproblemen
- angezeigte Fehlermeldung
- ob das Problem unmittelbar nach einer Änderung aufgetreten ist
Übermittle keine Passwörter oder andere Zugangsdaten innerhalb einer normalen Fehlerbeschreibung.
Summary #
About Files → File Manager kannst du Dateien deines CURIAWEB-Webhostings direkt im Browser hochladen, herunterladen und bearbeiten.
Öffne vor jeder Aktion den richtigen Dokumentenstamm und kontrolliere Dateiname sowie Dateiendung. Wenn eine vorhandene Datei ersetzt oder verändert werden soll, sichere die bisherige Version vorher.
Textbasierte Dateien kannst du direkt mit dem cPanel-Editor bearbeiten. Behalte dabei die bestehende Zeichencodierung bei und ändere möglichst nur eine Sache gleichzeitig.
Teste eine aktive Website unmittelbar nach jeder relevanten Änderung. Wenn anschließend ein Fehler auftritt, stelle zuerst den vorherigen Dateistand wieder her, anstatt weitere Dateien auf Verdacht zu verändern.
Für einzelne Dateien ist der cPanel-Dateimanager sehr praktisch. Bei großen oder regelmäßigen Übertragungen kann dagegen eine FTP-Verbindung die bessere Arbeitsweise sein.
