A WordPress install breaks down into three core folders and a few loose files in the root. wp-admin and wp-includes are WordPress core and off-limits to edits. wp-content is the one folder that's yours: themes, plugins, uploaded media, and cache files all live there. Here's what each piece does and when you should touch it.
The core folders
Every WordPress install has the same three top-level folders plus a handful of loose files in the root:
wp-admin- WordPress core. Runs your dashboard. Never edit files here; core updates overwrite the whole folder.wp-includes- WordPress core. Shared PHP libraries the software runs on. Same rule: never edit, never add files here.wp-content- the one folder that's actually yours. Themes, plugins, uploaded media, and cache files all live here. This is the only core folder you should ever open with intent to change something.
Inside wp-content, three subfolders matter most:
wp-content/themes- one subfolder per installed theme. Your active theme's template files live here.wp-content/plugins- one subfolder per installed plugin.wp-content/uploads- every image, PDF, and file uploaded through the media library, sorted intoYYYY/MMsubfolders by upload date.
In the root alongside those three folders you'll also find wp-config.php (database credentials and core settings), .htaccess (rewrite rules, mainly permalinks), and index.php (the front-door script that loads everything else). All three are small, all three matter, and all three are worth leaving alone unless you know exactly why you're changing them.
How to get to them
You don't need FTP for most of this. From your Flashcloud portal, open the service for your hosting account and launch File Manager. It gives you a browser-based view of the same filesystem, with upload, edit, and permission controls built in.
If you prefer a desktop client or need to move a lot of files at once, an FTP account works the same way. Create one from the FTP Accounts tile in the portal, then connect with any FTP client pointed at your domain.
Either way, you're looking at the same folders described above. File Manager is faster for quick edits and permission checks; FTP is better for bulk uploads or syncing a local project folder.
What's safe to edit, and what isn't
A few rules keep you out of trouble:
- Never edit wp-admin or wp-includes. Every core update replaces these wholesale. Any change you make there disappears on the next update, or breaks the update itself.
- Theme and plugin files get overwritten on update too. If you need to change a theme's PHP or CSS, use a child theme so your changes survive the parent theme's next update. If you need custom CSS only, a theme's built-in custom CSS option is safer than touching files at all.
- wp-config.php is powerful and unforgiving. A single typo (a missing semicolon, a stray character outside the PHP tags) takes the whole site down with a white screen. Edit it directly only when you have a specific reason, like adding a constant a plugin's documentation asks for, and always keep a copy of the working version before you save.
- Uploads is safe to browse, risky to hand-edit. Deleting files here that the media library still references breaks image links across your site. Manage media through the library, not the filesystem, unless you're cleaning up an orphaned mess.
For anything beyond viewing or a quick fix, do it through wp-admin. The block editor, Appearance settings, and Plugins page exist so you rarely need to touch these folders by hand.
Installing a plugin or theme manually
Almost everything installs through Plugins → Add New or Appearance → Themes → Add New in wp-admin, which handles the file placement for you. Manual installs are for the exceptions: a premium plugin you bought outside the WordPress.org directory, or a zip file a developer sent you directly.
wp-admin's uploader (the "Upload Plugin" or "Upload Theme" button on those same screens) takes a zip file and extracts it to the right folder automatically. That's the path to use first. File Manager is the fallback when a zip is too large for the upload limit or when you're restoring something from a backup.
When files aren't the problem
If a site is slow, that's rarely a filesystem issue. Check My WordPress site is slow; it covers caching, plugin weight, and image size as the usual causes. If you're about to make a change that could go sideways, such as a theme switch, a risky plugin update, or custom code, clone the site into a staging copy first. See Using WordPress staging for the workflow. And before any manual file edit you're not fully sure about, confirm your backups are current; see Backing up your WordPress site for what's already running on your account.
When to contact support
If you've broken something by editing a file directly and you're looking at a white screen, a fatal error, or a site that won't load, open a ticket from the portal (Support → New ticket) or use live chat. A real person can help restore a working version from backup, usually faster than you can track down a stray character in wp-config.php.