Access and Edit WordPress Files in MyKinsta Without an FTP Client
A hands-on guide to opening, editing, uploading, and organising WordPress files directly from the MyKinsta dashboard, with practical notes on backups, binary files, and activity tracking.
Picture a late-night scenario: a client site is throwing errors, the admin area is unreachable, and a single plugin folder needs to be renamed to deactivate the culprit. Reaching for a desktop FTP client means digging out SFTP credentials, configuring a new connection, and waiting for a directory tree to load just to perform a five-second task. MyKinsta includes a built-in file manager that removes that friction. It lets you browse, edit, upload, move, copy, rename, and delete WordPress files straight from the hosting dashboard, so everyday file work no longer requires a separate client.
For website owners who want to self host a WordPress website or simply manage one more efficiently, the dashboard approach also keeps a smaller software footprint on the server. That matters because WordPress file-management plugins have a rough security history, and a hosting-level tool sits outside WordPress entirely.
Key Takeaways
- MyKinsta's file manager lives outside WordPress, so it does not expand the site's attack surface.
- Take a manual backup through MyKinsta before renaming directories, deleting files, or editing configuration files.
- The built-in editor handles text-based formats such as PHP, HTML, CSS, JavaScript, JSON, XML, YAML, and SQL.
- Binary assets like images, videos, PDFs, archives, and fonts must be downloaded, edited locally, then re-uploaded.
- Every action in the file manager is recorded in the MyKinsta activity log for accountability.
Why Skip FTP for Everyday WordPress File Work
SFTP remains the right answer for heavy jobs such as migrating an entire site, running scripted deployments, or pushing thousands of files at once. For routine tasks, however, the setup overhead is disproportionate to the job. Spinning up a client, finding credentials, and waiting for the directory tree to load turns a small edit into a several-minute distraction.
Security is another reason to reconsider the typical workaround. When people want quick file access without a client, the common fallback has been a file manager plugin installed inside WordPress itself. That category of plugin has a poor track record. A widely deployed plugin called WP File Manager shipped a zero-day vulnerability in 2020 that scored 10.0 on the CVSS scale, the maximum possible severity rating. It let unauthenticated visitors upload PHP webshell files directly to the server with no login required, and exploitation began on the same day the disclosure went public. Wordfence reported that more than 700,000 WordPress sites were running affected versions at the time.
The deeper problem is the category itself. Any plugin that can read, write, and delete files across an entire installation is acting with considerable power, and powerful code inside WordPress inherits WordPress's full attack surface. Once an attacker bypasses authentication, a file manager plugin is exactly the tool they want waiting for them. A hosting-level file manager sidesteps that exposure because it lives in the dashboard, behind MyKinsta account credentials, and adds nothing to the live site.
Opening the MyKinsta File Manager Safely
Direct file access means there is no safety net between a mistake and a broken site, so backups come first. In MyKinsta, open Sites from the sidebar, choose the environment you want to work in, and click Backups. Create a manual backup and confirm it completed before touching anything else. A clean restore point turns any wrong click into a recoverable event rather than an outage.
When the backup is in place, return to Sites, pick the same environment, and open the Files tab. The file manager loads at the site's public directory, which is where WordPress resides in standard installations. If the public directory has been renamed or relocated, the manager opens at that renamed root instead.
The interface works like a familiar desktop file browser. Folders open with a click, breadcrumbs along the top let you walk back up the tree, and a kebab menu (the three-dot icon) next to each entry exposes the available actions. Symlinks appear next to regular files and directories, with their target path displayed so you always know where a link points.
Every change made in the file manager is captured in the MyKinsta activity log, found under User activity in the dashboard. For agencies and in-house teams where several people share access to the same site, that log quietly answers the question that always follows a breakage: who changed what, and when.
What the File Manager Can Do
The dashboard tool covers the everyday tasks that previously required a separate FTP client or a third-party plugin.
| Capability | How it works in MyKinsta | Best for |
|---|---|---|
| Browse and navigate | Click folders, follow breadcrumbs, scroll through entries; symlinks show their target path | Quick orientation inside a WordPress install |
| View and edit text files | Open PHP, HTML, CSS, JavaScript, JSON, XML, YAML, and SQL with a numbered-line editor | Fixing theme files, tweaking CSS, patching plugin code |
| Upload files | Pick multiple files at once; up to 2GB per file | Dropping in a fresh theme, plugin zip, or replacement asset |
| Move, copy, rename, delete | Triggered from the kebab menu on any entry | Deactivating a broken plugin by renaming its folder, reorganising assets |
| Track changes | Every action recorded in the MyKinsta activity log | Team accountability and post-incident review |
Editing Files Directly in the Dashboard
Click any filename to open it in read-only mode, or pick View from the kebab menu for the same effect. To make a change, either hit the Edit button inside the viewer or choose Edit directly from the kebab menu to jump straight into edit mode. The editor renders numbered lines, which helps when orienting yourself in longer files and when referencing a specific line in a debugger or support thread.
When the edit is finished, click Save changes. Updates take effect on the live site immediately, which is why that manual backup taken earlier really does earn its place.
Binary and media assets cannot be opened in the editor. To work on a PDF, image, video, archive, or font, download it through the file manager, edit it in a desktop application, and then upload it back to the same folder. Treating binary assets that way also keeps the editor focused on text-based formats where it can actually help.
Uploading, Renaming, and Replacing Files
To add new files, navigate to the destination folder and click Upload file. You can pick multiple files in a single selection, and they all land in the active folder. Each file has a maximum size of 2GB; anything bigger is a better job for SFTP.
Two practical notes keep uploads predictable. First, stay on the page until the progress indicator confirms completion, so a partial upload does not masquerade as a finished file. Second, when an upload target already exists in the folder, the existing file stays in place and the new one is not added. If a replacement is the goal, remove or rename the original first, then upload.
Renaming a plugin folder is one of the most useful everyday actions. It deactivates the plugin without touching the database, which is a fast recovery move when a site is locked out by a faulty update. The same approach works for switching a theme by renaming its directory, or for isolating a suspect mu-plugin by moving it out of wp-content/mu-plugins.
When an FTP Client Is Still Worth Using
The dashboard tool is not a wholesale replacement for SFTP. Bulk migrations, scripted deployments, automated syncing of large asset libraries, and uploads larger than 2GB per file all favour a dedicated client. Developers working from a local Git workflow also benefit from SFTP because it integrates cleanly with deployment scripts and continuous integration pipelines.
For everything else, the MyKinsta file manager is faster, simpler, and safer than installing a plugin inside WordPress to do the same job. If you are starting fresh and want a guide to the broader setup, the knowledge base walkthrough on how to install WordPress in your domain covers the surrounding steps.
Frequently Asked Questions
Does the MyKinsta file manager replace SFTP entirely?
No. It covers everyday browsing, editing, uploading, and housekeeping tasks without leaving the dashboard. For bulk migrations, scripted deployments, or moving files larger than 2GB, an SFTP client is still the more capable tool.
Can the file manager edit WordPress core files safely?
Yes, the editor handles text-based formats such as PHP, HTML, CSS, and JavaScript. Because changes apply to the live site immediately, taking a manual backup before editing core, theme, or configuration files is strongly recommended so any edit can be reversed.
What happens when a file with the same name already exists in the upload folder?
The existing file is preserved and the new upload is not added. To replace a file, rename or remove the original first, then upload the replacement. Staying on the upload page until progress completes also helps avoid partial uploads.
Why prefer the MyKinsta file manager over a WordPress file manager plugin?
A hosting-level tool lives outside WordPress and is protected by MyKinsta account credentials, so it does not add to the site's attack surface. File manager plugins run inside WordPress, and that category has a history of severe vulnerabilities, including a 2020 zero-day in a widely used plugin that allowed unauthenticated file uploads.
Is there a record of who changed which file?
Yes. Every action performed in the file manager is written to the MyKinsta activity log under User activity. For teams and agencies, that log is a quick way to trace a breakage back to the exact change and the user who made it.
Action Checklist Before You Start Editing
- Open MyKinsta and create a manual backup of the environment you plan to edit.
- Navigate to Sites, pick the environment, and open the Files tab.
- Confirm you are inside the correct folder before editing, renaming, or deleting anything.
- Use the kebab menu for move, copy, rename, and delete actions to keep the workflow consistent.
- For binary assets, download, edit locally, then re-upload rather than opening them in the editor.
- Review the activity log afterwards if you need to confirm or audit the changes made.
- If something goes wrong, restore the manual backup taken at the start of the session.
If a recent edit has already pushed a site into a critical state, the practical recovery steps in how to fix critical error in WordPress pair well with the file manager workflow. For ongoing protection at the network edge, the guidance on Cloudflare waf WordPress vulnerabilities explains how a managed WAF can block the kind of file-upload exploits that motivated hosting-level tools in the first place. Staying current with platform releases also helps; the recent look at WordPress 7 1 beta 3 what to test is a useful companion read while you are inside the dashboard.
