I uploaded some media files via FTP to my WordPress site, but I can’t see them in the media library. I need to know how to properly add these files to the media library so they’re usable in WordPress. How can I fix this issue?
For those tackling the particular challenge mentioned, a strategic solution worth exploring is the CloudMounter app. This tool stands out for its ability to seamlessly integrate with your existing workflow, offering a versatile platform for managing cloud services and remote drives directly from your computer. With its straightforward design and extensive compatibility, it’s an efficient option to address the described task.
2 Likes
Well, uploading files via FTP and not seeing them in the WordPress Media Library is like sending a package but forgetting to tell the recipient where to look for it. Unfortunately, WordPress doesn’t automatically recognize files you’ve uploaded via FTP because it stores media file references in its database. Without this step, the Media Library won’t display your files. Here’s how you can fix it:
1. Use a Plugin
The most straightforward way to ‘register’ those files into the Media Library is by using a WordPress plugin like “Add From Server” or “Media Sync.” These plugins scan your upload directory for new files and then add them to your Media Library—no coding required.
Steps:
- Install and activate the plugin.
- Use the plugin to locate your newly uploaded FTP files.
- Select the files you want to add, and they’ll show up in your Media Library.
2. Manually Register Files
For the brave ones: if you’re okay with digging into code, you can write a custom PHP script—though, let’s be real, not the most fun way. This script can use the wp_insert_attachment function to register your media files into the WordPress database. Just be careful, or you might cause a mess (or worse, break your site).
3. Correct Upload Path
If WordPress isn’t even looking in the right place for your uploaded files, check the file path. Go to Settings > Media, and ensure that the “store uploads in this folder” option matches where you’ve uploaded via FTP (usually wp-content/uploads/[year]/[month]/). If this doesn’t match, WordPress won’t even realize the files are there.
4. Verify Permissions
Double-check that the directory and files have the correct permissions (like 755 for directories and 644 for files). Sometimes, incorrect permissions can block WordPress from accessing or displaying the files correctly.
5. Regarding Cloud Solutions
While @mikeappsreviewer suggested integrating tools like CloudMounter, which is excellent for managing cloud services and remote drives, I think it’s overkill if you’re dealing with a handful of files uploaded via FTP for WordPress. However, if managing external storage sources is common for you, simplifying your cloud workflows can be beneficial in the long run.
Honestly, plugins like “Media Sync” will spare you a headache unless you’re in a ‘DIY or bust’ kind of mood. The key here is to register those files properly in WordPress—FTP itself won’t finish the job.
Alright, so here’s the raw truth: WordPress just doesn’t care about those files you FTP’d unless you formally introduce them to each other. It’s like trying to RSVP to a party you weren’t officially invited to—it’s awkward for everyone involved. And no, WordPress won’t find them on its own no matter how long you stare at the media library.
Okay, let’s keep it simple and practical here. I saw @mikeappsreviewer and @shizuka shared some good points, but I’ll add a few alternative hacks. Here’s what you can do:
1. Plugins are your best bet
Sure, plugins like “Add From Server” and “Media Sync” work well, but do you really need another plugin bloating your site? If you don’t mind, go for it—it’s fast and saves you from touching code. But for those of us who are paranoid about plugins slowing down our site, skip to the next solutions.
2. Direct Database Insertion
Okay, hear me out. If you’re comfy poking around in SQL databases (or not terrified to try), you can directly add references for your FTP’d files to WordPress.
Steps:
- Go to PHPMyAdmin (or whichever tool you like for managing databases).
- Find the wp_posts table in your WordPress database.
- Insert a new entry with:
post_type = ‘attachment’,
guid = your-file-URL,
and set post_mime_type to match (e.g., image/jpeg for JPEGs).
Now don’t mess this up unless you enjoy breaking your site on a Friday night.
3. Try Command Line Tools (Advanced users)
If you’re into terminal work, consider using WP-CLI. It’s basically WordPress management wizardry via command line. Specifically, you can use:
wp media import /path/to/your/files/*
This command will scan your uploads folder on the server and register files to your Media Library. Efficient, right? But maybe overkill if FTP’d files are a one-time thing for you.
4. Embrace the Cloud
Sooo, if uploading and managing local files via FTP feels ancient (which btw, it is), why not use something modern like streamlining your cloud storage? CloudMounter makes connecting WordPress with external drives or cloud services way easier. Still not convinced? Fine, you do you, but my FTP days are long gone.
5. Check Folder Permissions & Paths
Basic, but often overlooked. Make sure those uploaded files are sitting in the DEFAULT uploads folder (something like /wp-content/uploads/2023/10/). Anything outside of WordPress’s standard structure might cause problems. And, oh, don’t forget file permissions—chmod to 644 for files and 755 for folders. If that doesn’t mean anything to you, Google it. 
In my opinion, plugins might be the simplest way to fix this, even if @shizuka suggested some overly complex manual adjustments that aren’t worth it unless you’re a developer at heart. And for CloudMounter fans like @mikeappsreviewer pushing it, sure, it’s fab for external integration—but FTP itself ain’t gonna demand cloud managers unless you like applying overkill solutions.
So yeah, tools like “Media Sync” or the WP-CLI command are solid choices if you want functional solutions without breaking things. STOP manually coding unless you’re masochistic. Your future self will thank you.
Use WordPress’s built-in uploader instead of registering FTP files.
Download the FTP files to your computer. In WordPress, open Media, Add New, then drag the files into the upload area. WordPress creates the database records, thumbnails, and metadata for you.
After confirming they appear in Media Library, delete the old FTP copies to prevent duplicates. Upload files in smaller batches, such as 20 at a time. It’s a bit repetitive, but safer and simpler for a one-time import.
The direct database insertion trick from @byteguru will get files showing up, but it skips the part that actually matters: attachment metadata. WordPress stores image dimensions, alt text hooks, and the list of generated sizes in a postmeta field called _wp_attachment_metadata. Skip that and your images register as attachments but come out broken when you try to insert them into a post, because the thumbnail and medium sizes don’t exist. So you end up ‘fixing’ the library only to fight a second problem later.
Small correction on the WP-CLI advice too. wp media import doesn’t just scan and register files that are already sitting in your uploads folder. When you point it at a local path it copies those files into the media library as fresh uploads, usually renaming them in the process. Handy, but you can end up with duplicates of what you FTP’d, so you’d want to delete the originals after. If the goal is to register files in place without moving them, ‘Media Sync’ or ‘Add From Server’ is closer to what you actually want, and both run the metadata generation for you.
The thing nobody mentioned: if you’re dealing with a batch of images and thumbnails still look off afterward, run a thumbnail regeneration. WP-CLI has wp media regenerate for exactly that, or a plugin like Regenerate Thumbnails does the same. That’s the step people forget after any bulk import.
On CloudMounter, it came up a couple times already and I get why. Mounting your storage as a drive makes the FTP part less painful if you move files around a lot. But it lives on the connection side of the problem. It gets files onto the server, it doesn’t register anything in the WordPress database, so you’d still need one of the methods above afterward. Useful for the transfer, not a fix for the library itself.
Honestly, for a one-time import @primephoenix_36 has the least risky call. Pulling the files back down and using the normal uploader means WordPress builds every record and size correctly and you never touch SQL. Slower, a bit dull, but it just works. I’d only skip that route if you’ve got hundreds of files, in which case Media Sync plus a thumbnail regen is the sane middle ground.