WP Media Folder - WordPress Plugin

Guide to Configuring and Using WP Media Folder

WP Media Folder is not just there to add one more menu item to the WordPress admin area. Its real value shows up when the media library has already become a working archive: product images, campaign banners, PDFs, logos, article covers, older image versions, and assets uploaded by different contributors. In this guide, we will look at how to turn that kind of library into a clear system of folders, filters, galleries, and checks without relying on chaotic manual sorting.

Below you will find a practical walkthrough: what to check before installation, which settings to enable first, how to build a folder structure, how to use filters, how to create a gallery from a folder, why physical folders can be risky, how to diagnose issues, and when it makes sense to look at similar solutions. This guide does not replace the official documentation, but it helps connect individual features into a workable process for a real website.

It is also important to understand where the product stops. WP Media Folder works around the standard WordPress media library and extends it with folders, sorting, filters, access control, file replacement, galleries, imports, server synchronization, and cloud workflows through an addon. It is not a standalone file manager for your entire server, and it is not a plugin for protecting private downloads. That is why proper setup starts with understanding the exact problem you are trying to solve.

If your site only has a few dozen images, some of its features may be more than you need. But for content-heavy projects, WooCommerce stores, training portals, documentation sites, portfolios, and team-based editorial workflows, the plugin solves a painful everyday problem: finding the right file quickly, avoiding duplicate uploads, not breaking an image that is already in use, and keeping control over who can see and move media.

What Problem the Plugin Solves in the WordPress Media Library

The default WordPress media library stores attachments as attachment post types and displays them in a grid or list. For a small site, that is usually enough: you can search by name, filter by month, and insert an image into a post. The problem begins when media becomes part of an actual production workflow. An editor is looking for an old banner, a store manager uploads new product photos, a designer replaces a logo, a course author adds a PDF to a lesson, and an administrator is trying to figure out which files are already in use.

WP Media Folder adds an organization layer on top of that familiar environment. The main layer is virtual folders inside the media library. The key word here is virtual: moving a file between folders in normal mode should not break inserted URLs, because WordPress still works with its original attachment records. That is very different from manually dragging files around on the server over FTP, after which the media library may no longer see those files or may lose the relationship to them.

The plugin is especially useful when the same file needs to appear in multiple places. The documentation describes the ability to assign one media file to several folders. A practical example: a product photo can live in a category folder, a seasonal campaign folder, and a folder for homepage assets. There is no need to upload three copies of the same image. On sites with large numbers of banners and product cards, that reduces the risk of duplicates.

The second major task is search and filtering. WP Media Folder adds filters by media type, date, pixel dimensions, file size, whether a file is attached to a post or page, plus sorting for both folders and files. This is not some magical site optimization feature, but the difference in day-to-day editorial work is noticeable: instead of scrolling through hundreds of thumbnails, you can narrow the view down to a specific folder, file subtype, and size range.

The third task is safely updating files that are already being used. On its product page, JoomUnited specifically documents media replacement while keeping the same URL. That matters when a file is used across multiple pages but its contents need to be updated, for example when replacing a PDF catalog, updating a delivery map, or uploading a corrected infographic. Instead of deleting the old file and replacing links manually, you can use the replace mechanism, but you should still make a backup first and verify the result on the live pages.

Who WP Media Folder Fits Best, and When It May Be Unnecessary

The plugin works best on sites where media is not a one-time upload but a permanent operational layer. That includes WooCommerce stores with large product catalogs and variations, magazines and blogs with publication archives, schools and courses with PDFs and illustrations, agency sites with portfolios, corporate portals with documents, landing pages, and campaigns. On projects like these, the value does not come from a single feature, but from the combined effect of many small ones: folders, bulk moves, filters, subfolder search, galleries, access permissions, structure import, and clean file replacement.

Team-based sites should pay attention to folder access restrictions by user or role. The documentation describes permissions for viewing folders, adding, renaming, deleting, viewing other users' media, moving media, and updating file information. That is useful when a course editor should not see all marketing assets, or when a store manager only works with product images.

WP Media Folder is also a good fit for sites that already use page builders. The official page lists compatibility with Gutenberg, Elementor, Divi, WPBakery, Avada, and a range of multilingual solutions. But the word compatibility does not mean you should enable every feature without testing. If the site is built around a frontend editor, the WP Media Folder on frontend setting should only be enabled when you actually need it. The documentation is explicit: if you do not need the plugin to operate on the frontend, it is better to leave that option off for performance reasons.

When might the plugin be unnecessary? First, on small sites where the media library is not growing and the entire archive fits on a few screens. Second, for projects that do not need a media library organizer but instead need a protected file area with private downloads, document-level access permissions, and download logs. JoomUnited offers a different product for that, WP File Download, and the wider WordPress ecosystem also has dedicated document library and membership solutions. Third, for sites where owners expect traditional server folders like they see in a desktop file browser. WP Media Folder does offer a mode like that, but it requires caution and is not a good fit for every setup.

Practical rule of thumb: if your main pain point is finding, classifying, reusing, and replacing media inside WordPress, WP Media Folder is a good fit. If you need protected file delivery, complex download permissions, or a full DAM across multiple websites, start by looking at a different class of tools.

What to Check Before Installation and Initial Setup

You do not need to turn preparation into a week-long audit, but a few checks will save time. First, assess the scale of your media library: how many files there are, what media types you use, whether old duplicates exist, who uploads assets, and which editors search for files most often. That will help you avoid building folders around random logic. Your folder structure should reflect actual workflows, not just a nice-looking hierarchy.

The second step is backup. Even if you plan to use only virtual folders, media is a critical part of the site. Before importing, bulk moving, replacing files, enabling a watermark, turning on server folder sync, or using physical folders, back up both the database and the uploads directory. This is especially important on older sites where image links may appear not only in content, but also in builder fields, theme meta fields, widgets, and third-party tables.

The third step is checking compatibility with your editor and theme. In normal mode, WP Media Folder integrates into the standard WordPress media manager. If your site uses Gutenberg, Classic Editor, Elementor, Divi, or WPBakery, test image insertion through the actual tool your team uses every day. Do not stop at the settings page. Open a post, select an image from a folder, insert it, save, and verify the public-facing page.

The fourth step is deciding whether you actually need addon features. Cloud connectors, offload, PDF embedder, and the gallery addon belong to more advanced workflows. You should not enable them just because they appear in the feature list. Cloud storage requires its own setup, background jobs, and synchronization monitoring. Galleries require testing with your theme, lightbox, responsiveness, and performance. PDF embedding requires checking how it renders on mobile and how caching affects it.

The fifth step is agreeing on naming rules. WP Media Folder supports renaming and AI optimization for file names, alt text, descriptions, and captions, but that does not replace editorial logic. If your site includes products, campaigns, and multilingual content, decide in advance which words should appear in a filename, when to use a SKU, when to use a category, and when to include a short description. Automation is only useful when it strengthens a system that already makes sense.

Installation and the First Check After Activation

Installation works like any standard commercial WordPress plugin: in the admin area, go to Plugins, then Add New, upload the ZIP archive through Upload Plugin, install it, and activate it. This guide intentionally does not cover purchasing, account management, or licensing steps. From a practical standpoint, what matters is something else: after activation, make sure the media library opens correctly, the folder panel appears, and the core actions do not conflict with your theme or editor.

After activation, go to Media - Library. If the plugin is working properly, the media library should now show a left-hand folder panel, folder creation buttons, and additional controls. Create a test folder, for example Test Media Structure, upload one image and one PDF into it, then switch between grid and list view. The goal is not to organize everything at once, but to verify the basic flow: the folder is created, files go to the selected location, and search and filters do not break the display.

Next, open a post or page and try inserting an image from the folder you created. In Gutenberg, use the normal image block or media manager; in Classic Editor, use the Add Media button. If you work in a page builder, test its actual media field. After saving the page, open the public side of the site in a new window and make sure the image loads, the path is intact, and the correct size is being used.

After that, delete the test folder without deleting the file inside it. According to the documentation, when you delete a folder containing media, the files return to the root of the media manager by default. This is an important check for editors: a folder is an organizational layer, not a trash bin. If you enable the option to delete the folder together with its media, the risk is higher, so that mode should only be used by an administrator who fully understands the consequences.

Folder Logic: How to Build a Structure That Is Easy to Maintain

The most common mistake when introducing media folders is trying to copy your desktop file structure directly into WordPress. That structure may make sense to a designer on a local drive, but in the media library, the people working with it are editors, managers, and content authors. Folders should help them choose the right file at the moment of publication. So start with workflows, not an abstract hierarchy.

For a content site, it often makes sense to split media by broad types: Blog, Guides, Landing Pages, Brand Assets, Documents. Inside those, you can add a year or topical categories if that genuinely speeds up search. For a WooCommerce store, a more practical structure is based on product categories, brands, seasonal campaigns, and operational assets: Products, Category Banners, Sale Campaigns, Size Charts, PDF Manuals. For an education project, use courses, modules, lessons, and shared templates.

Do not build an overly deep tree. If an editor has to open five levels just to find a cover image, the structure is already slowing work down. In most cases, it is better to use two or three folder levels and support them with filters, search, tags, and clear filenames. WP Media Folder supports search within a folder and its subfolders, so depth is only useful when it reflects the real organization of the project.

Folder color and the context menu help people orient themselves quickly, but color should never be the only classification method. Use it as an additional signal: for example, red for seasonal campaigns, green for evergreen assets, blue for documents. The folder name still needs to make sense on its own, because different users perceive interfaces differently.

A Folder Is Not the Same as a URL

In normal virtual mode, moving media between folders does not mean the file was physically moved into a different server directory. That is good for already published content: links should not break. But it also means the folder structure in the media library and the structure inside wp-content/uploads may be different. Do not promise your team they will see the same structure over FTP unless you have explicitly enabled the separate physical folders mode.

One File Across Multiple Working Contexts

If an image is used in several parts of the site, do not upload it again. Assign it to multiple folders using the folder selector in the right column or through bulk selection. This is especially useful for logos, certificates, product images reused across campaigns, and visuals that appear on multiple landing pages. The key check after assigning a file this way is making sure there is still only one file and that editors can see it in all the contexts where they need it.

Post-Install Settings: What to Enable Right Away and What to Leave Off

The settings area lives under Settings - WP Media Folder. In the documentation, it is divided into general settings, filtering, folders for post types, galleries, access, import/export, server folder sync, single file design, renaming, watermark, and WPML. You do not need to switch everything on. It is better to move from a safe core setup toward the more risky features.

General and Main Settings

Enable Enable folder tree if you want the folder panel inside the media manager. For most sites, this is a core feature. Display folder ID is useful for administrators, integrators, and developers, but it can add noise for a regular editor. Hover image is convenient for quickly checking thumbnails, dimensions, and metadata, although on weaker computers or extremely large libraries it is worth testing separately.

Only enable WP Media Folder on frontend if your builder truly works with the media manager on the public-facing side of the site. If you are not using a frontend editor, leave it off. This setting is not about whether visitors can see images; it controls whether the plugin's editing features need to load for frontend editing workflows.

Media Filtering

Filters by type, dimensions, file size, and date are worth enabling on almost any site. They are especially useful for finding large files, old PDFs, archives, unattached images, and media in a specific format. Set size and weight ranges to match your site. For example, on a blog you might separate cover images, illustrations, and heavy originals; in a store, you might separate product photos, category banners, and operational documents.

The option to search within a folder and its subfolders is helpful if your structure has nesting. Without it, an editor may search in a parent folder and not understand why the file is stored in a subfolder but does not appear in results. After enabling it, test search by part of a filename and by the attachment title.

Folder Settings for Posts, Pages, and Products

WP Media Folder can enable folders not only for media, but also for posts, pages, WooCommerce products, and some custom types. Turn this on only if your team has a real need to sort the posts or products themselves inside the admin area. For a store with hundreds of products, that may be useful; for a simple blog, it only adds another layer. Start with the media library, then expand the scope later if it proves necessary.

Media Access

User- or role-based access restrictions are useful on team sites. If you enable this mode, first create a test role or test user, log in with that account, and verify exactly what happens: which folders are visible, whether subfolders can be created, whether someone can move other people's media, and whether alt text and captions can be updated. Do not configure permissions only while logged in as an administrator, because administrators see far more than editors do.

Gallery Features

Folder-based galleries are useful when a folder itself becomes the source of a visual block on the page. Enable the gallery feature and lightbox if you plan to publish image collections. If your theme already applies heavy styling to the default WordPress gallery, check for CSS conflicts. The documentation notes that the default gallery can override the standard gallery; if that conflicts with your theme, it is better to disable the feature or apply it selectively.

Rename and Watermark

Automatic rename on upload and watermarking are powerful features, but they are not something to enable casually. Renaming is useful for SEO and search when the pattern is clear, for example a product name, category, and short description. Watermarking may be useful for photographers, portfolios, and catalogs, but it applies to images and thumbnails according to specific rules. Before applying a watermark in bulk, always test a copy of the image and every thumbnail size, otherwise you may end up with an unwanted mark on tiny previews or technical images.

Filters, Sorting, and Search: How Not to Get Lost in Thousands of Files

In WP Media Folder, filters are best understood as an editor's control panel. Folders answer the question of where a file belongs conceptually. Filters answer the question of which file is needed right now. In large media libraries, those are different problems. A folder like Product Photos may contain hundreds of images, but a filter by size, type, and name can quickly narrow the results to the exact group you need.

In the media library, use type filters when you need to separate images from PDFs, archives, videos, or unattached files. Date filtering helps when the team remembers roughly when campaign materials were uploaded. File size filters are useful for auditing heavy images. Minimum pixel dimensions help you avoid inserting a small image into a hero block where it would look blurry on a wide screen.

Sorting folders by name is useful when you want a stable tree, sorting by ID can help administrators identify newly created folders, and custom order works well for teams that care about workflow priorities. Sorting media by date, name, size, type, or custom order helps when preparing a gallery, reviewing recent uploads, or finding heavy files. The documentation notes that the selected order is stored in the session through a cookie, so an editor can return to the view they are used to.

How to Search in Subfolders

If your structure includes nesting, enable search within a folder and its subfolders. Then test it with a simple example: place a file in the Campaigns / Spring subfolder, open the parent folder Campaigns, and search for the file using part of its name. If search works only in the current folder, editors will assume the file disappeared. If it searches subfolders as well, the tree becomes much more useful without getting too deep.

The Attached File Filter

The Attached to filter is useful when you need to understand which images are associated with a specific post or page. It is not a full audit of every mention of that file in the database, but as an editorial tool it helps you quickly review the assets tied to a given piece of content. For example, before updating an older guide, you can check which images were attached to that page and decide which ones need to be replaced or moved.

Do not expect filters to compensate for bad filenames. If your images are named IMG_1234.jpg and final-final-new.png, even a good filter will not make the library understandable. First agree on naming conventions, then strengthen the workflow with filters.

Folder-Based Galleries and Gutenberg: When a Folder Becomes the Source of a Block

One of WP Media Folder's product-specific strengths is the ability to create galleries from folders. That is useful when a collection of images should live as a managed set. Examples include a project portfolio, event photo gallery, product image collection, lesson illustration series, or a video selection. Instead of manually picking images every time, you can rely on the folder and update the contents directly through the media library.

The documentation describes several paths: creating a gallery from a folder in the media manager, working with the gallery in Gutenberg through the WP Media Folder Gallery block, and configuring gallery themes, columns, thumbnail sizes, lightbox behavior, click actions, sorting, and display order. There are options for the Classic Editor and the default gallery too, but on modern sites it is usually easier to validate the workflow through blocks.

A practical workflow looks like this. First create a folder, for example Project Case Study, and upload only the images that should appear in the gallery. Then open the page, add a block from the WP Media Folder group, select the folder, and create the gallery. Configure the theme: masonry works well for mixed aspect ratios, slider suits a compact visual block, and default or portfolio works better for a more structured grid. After saving the page, open the public page and check not only the desktop view, but the mobile version as well.

What to Check After Inserting a Gallery

Your validation should be specific. Open the page in a browser while logged out of admin mode, check the image order, image click behavior, lightbox, captions, mobile responsiveness, loading speed, and caching behavior. If the gallery sits inside a tab, accordion, or builder slider, test it in that exact location. WP Media Folder's changelog has included fixes related to galleries inside page builders and to mobile rendering, so this is worth verifying directly.

If the gallery is supposed to update automatically when new images are added to the folder, upload a new image to that folder, clear the page cache, and check the result. If the page uses aggressive caching or image optimization, the change may not appear immediately. In that case, the problem is not necessarily WP Media Folder itself: you also need to check the optimization plugin cache, the CDN, lazy loading, and your theme settings.

Video and PDF in Media Workflows

WP Media Folder can add remote video from sources such as YouTube, Vimeo, Dailymotion, and other supported platforms when the feature is enabled in settings. That is convenient for editors because the video appears alongside other media and can take part in visual workflows. But in most cases, you should not store heavy videos directly inside WordPress. For public playback, it is usually better to use a dedicated video host and insert or link the remote video in WordPress.

PDF embed in Gutenberg belongs to addon-based workflows. It is useful for instructions, catalogs, menus, documents, and course materials. After inserting a PDF, check the block height, scrolling behavior, mobile readability, and how it behaves inside page builders. If the document should also be downloadable, make sure the user can clearly find the download path and that the file does not conflict with separate document protection plugins.

Cloud, Server Sync, and Physical Folders: Powerful Modes That Should Not Be Rushed

WP Media Folder's advanced modes offer a lot of flexibility, but they are also the ones that require the most careful testing. The Cloud addon connects Google Drive, Dropbox, OneDrive, Amazon S3, DigitalOcean, Linode, Wasabi, Google Cloud, Nextcloud, Cloudflare R2, and other storage platforms depending on the integrations available. Server folder sync helps synchronize a server folder with WP Media Folder. Physical folders turn virtual folders into real folders and change file paths.

These modes solve different problems. Cloud is for cases where media should live in cloud storage, be synchronized there, or be offloaded from the server. Server sync is for situations where files already reach the server outside the media library and need to be indexed into WordPress. Physical folders are for people who specifically need a server-side folder structure, but that comes with file and link changes. Do not enable one mode in place of another just because the names sound similar.

Cloud Sync and Background Jobs

The Cloud Addon documentation describes synchronization settings such as the method through AJAX or a crontab URL, sync frequency, manual full synchronization, and the JoomUnited background queue. The practical takeaway is simple: on a small site, the default settings are often fine as long as you first test them on a sample folder. On a large site, synchronization should not compete with regular visitors for server resources.

For large libraries, start with one test folder and a small file set. Check how the sync icon is displayed, what happens after a manual Run full synchronization, which notices appear, how long it takes for files to show up in the media library, and whether timeouts occur. If the server is weak, reduce the background queue speed or move execution to cron only after you fully understand how the mechanism behaves.

Server Folder Sync

Server Folder Sync lets you link a server folder with a WP Media Folder folder. In settings, you choose the sync direction, source, destination, and delay. This is useful, for example, when images arrive through an external workflow, from an older site, or from a manually uploaded directory. But it should not replace the normal media upload flow for everyday editors.

Before enabling it, make a list of the sources involved: which folders will sync, which file types are allowed, who is responsible for clean naming, and what should happen to deleted files. The changelog has included fixes related to server sync and duplicate images, so on older installations it is especially important to use an up-to-date version and test the process on a copy of the site first.

Physical Folders as a High-Risk Mode

Physical folders are the most sensitive mode. The official documentation warns that the feature moves media from virtual folders into real ones and edits file names; some plugin features may be incompatible with this setting. It also states that the mode is not compatible with WordPress multisite. This is not an ordinary checkbox for tidying things up, but a migration tool.

Before enabling physical folders, always back up the database and uploads, test on a staging copy, disable unnecessary caching, make sure the site is not running multisite, and prepare a rollback plan. Settings such as searching across the entire database, replacing relative paths, and selecting specific tables should only be enabled for a clear reason. If you do not know where your site stores image URLs, it is better not to enable advanced search across all tables on a live site.

Practical Example: Organizing a WooCommerce Store Media Library

Let us walk through a real scenario, because this is where it becomes clear how to use WP Media Folder as a workflow rather than just a set of checkboxes. Suppose you have a store with categories such as Shoes, Bags, Accessories, plus seasonal banners and PDF size guides. The team frequently searches for product images, uploads duplicate banners, and loses track of which version of a size chart is current.

Goal

You need to create a media structure where a store manager can quickly find product images, the marketer can see campaign banners, and the editor does not upload the same PDF documents again. At the same time, already published images must not break, and a test product card should still display the correct image after files are moved between folders.

Preparation

Before you begin, make a backup. Then create a simple structure: WooCommerce / Products / Shoes, WooCommerce / Products / Bags, WooCommerce / Campaigns, WooCommerce / Size Guides, Brand Assets. Do not enable physical folders. At this stage, use virtual folders, because the goal is admin-side organization, not changing server paths.

Steps

1. Open Media - Library and create a top-level folder called WooCommerce.
2. Create subfolders for products, campaigns, and documents, without going deeper than three levels.
3. Select several shoe images through Bulk Select and move them into Products / Shoes.
4. Assign one shared banner to the Campaigns folder as well if it is used both in a category and on the homepage.
5. Enable file type and file size filters to separate PDF size guides from product images.
6. Open a test WooCommerce product, select an image from the folder, and save the product card.
7. Check the public product page, the catalog thumbnail, and the enlarged image if your theme uses a lightbox.

Verify the Result

The result is successful if the manager can open a category folder, find the needed image through a filter, insert it into a product, and see that image on the site. Also verify that older pages where the moved files were already used still display their images. In virtual mode, folder-based organization should not break URLs, but the check matters because it rules out conflicts with the theme, cache, or optimization tools.

Nuance

If the image does not appear inside the product builder after it has been moved into a folder, check whether that field uses the standard WordPress media manager. The official page claims compatibility with popular builders, but individual fields from third-party plugins may behave differently. In that case, test not only the media library itself, but also the specific product field, variation field, or gallery field where the team actually selects images.

Mini-summary of the scenario: first build a clear folder structure, then enable filters, and only after that verify insertion into a real site entity. Bulk-oriented modes such as physical folders and server sync are not necessary in this workflow.

SEO, Performance, and Security: What You Can Actually Control

WP Media Folder affects SEO and performance not as a full-site optimizer, but through media workflows. The official page and documentation describe automatic renaming, AI-generated title, alt, description, and caption fields, WebP and SEO workflows on product pages, file replacement without broken links, thumbnail regeneration, watermarking, and the option to disable the plugin's frontend assets when they are not needed. All of that can be useful, but only when handled carefully.

Alt Text, Titles, and AI Descriptions

WP Media Folder's AI tools can fill in image titles, alt text, descriptions, and captions. The documentation notes that AI content is generated in the site's default language or in the language selected in settings. That is convenient for large libraries, but it does not remove the need for editorial review. Alt text should describe the image in the context of the page, not just repeat the product name or a target keyword.

If you enable Image info override, be careful: existing information may be overwritten. On a site where alt text and captions are already curated, test the feature on a separate folder first. For new uploads, AI optimization can be useful, but for older files it is better to process them in batches by folder so you can control the result step by step.

File Renaming

Automatic renaming on upload helps you move away from random names like IMG_7341.jpg. But overly aggressive templates can create long, awkward filenames. A good pattern stays short: asset type, object, important characteristic. For a store, for example: shoes-model-color-angle. For a blog: guide-topic-step. Do not stuff every page keyword into the filename.

Watermark

Watermarking in WP Media Folder can be applied to the entire library, to selected image sizes, or to selected folders. You can configure the scale, margin, opacity, and position. That is useful for portfolios, photographers, catalog images, and visual assets that are frequently copied. But a watermark is not a complete copyright protection solution, and it can make small previews look worse. Apply it selectively and verify every thumbnail size.

Performance

The plugin itself does not guarantee a faster site. Performance depends on image size, format, caching, CDN, lazy loading, theme behavior, and the server. WP Media Folder helps indirectly: it makes it easier to find heavy files, replace them, avoid duplicates, organize galleries, and, when needed, use cloud or offload workflows. If performance is the goal, measure the page before and after changes instead of assuming the media plugin alone will improve it.

Access Security

Restricting folders by role and user helps prevent editors from seeing media they do not need. But that is not the same thing as protecting files from direct URL access. If a document must stay private, you need a separate access model that controls downloads and direct links. WP Media Folder handles admin-side organization and permissions inside the media library, not every aspect of public-side file protection.

Common WP Media Folder Problems and How to Diagnose Them

Most problems with media folders are not caused by a single issue, but by several layers intersecting: the WordPress media manager, user permissions, cache, page builder behavior, cloud sync, outdated plugin versions, JavaScript conflicts, or settings that are simply too risky. Below is a practical symptom-based troubleshooting guide.

The Folder Was Created, but the Editor Cannot See It

Symptom: the administrator can see the folder in the media library, but an editor or author either cannot see it or cannot add files to it.

Possible cause: access restrictions by user or role are enabled, the folder inherits permissions from its parent, or the user is looking at the wrong root section. The documentation for folder permissions includes separate rights for viewing, adding, moving, deleting, and updating media information.

What to check: go to Settings - WP Media Folder - Access & Design - Media Access, then right-click the folder and review Permission settings. Log in as a test user with the target role and repeat the action.

How to fix it: configure permission inheritance correctly or explicitly add the role to the folder permissions. If the team is just getting started, begin with a simple model: administrators see everything, editors see shared working folders, and authors see their own folders. After changing permissions, test again under a real user account.

The File Was Moved, but Search Cannot Find It

Symptom: the file is definitely inside a subfolder, but it does not appear when searching from the parent folder.

Possible cause: search works only in the current folder, and the subfolder search option is disabled. The problem may also come from the filename itself: the editor is searching for words that do not exist in the filename or the title.

What to check: verify whether search within a folder and its subfolders is enabled in the general settings. Then try searching by an exact part of the filename and by the attachment title.

How to fix it: enable subfolder search and start renaming badly named files on future uploads using a clear naming template. For files that are already published, use renaming carefully and only after checking links.

The Gallery Did Not Update After Adding an Image to the Folder

Symptom: a new image was added to the folder, but the gallery on the page still shows the old set.

Possible cause: the page is cached, the gallery was created as a fixed selection, the block was not updated, or the theme or builder keeps its own cache. The changelog includes fixes related to galleries, mobile sliders, and page builder workflows, so the installed version matters too.

What to check: open the gallery block in the editor, verify the source, save the page, clear the page cache and CDN, then open the public page in incognito mode. Check the mobile version too if the issue is specific to the slider or lightbox.

How to fix it: update the block, clear cache, and verify the gallery feature and lightbox settings. If the problem persists only inside one specific builder, temporarily test the same image set in a normal Gutenberg block so you can separate a plugin problem from a builder problem.

Remote Video Is Not Added or Does Not Open

Symptom: the button for adding remote video is missing, the link does not load, or the video does not open in the lightbox.

Possible cause: the remote video feature is disabled under General - Main Settings, the video source is unsupported, the link is unavailable, or the plugin version is outdated. The changelog includes separate fixes related to YouTube and Vimeo.

What to check: verify that the remote video feature is enabled, that the link works in the browser, that the source is supported, and that there is no blocking from a privacy or cookie plugin or from CSP settings.

How to fix it: enable the feature, use a clean video URL, update the plugin, and test without conflicting optimization layers. If the video is heavy or important to a public-facing page, it is usually better to host it on a video platform and use a WordPress embed or a supported remote video workflow.

Broken Images Appeared After Enabling Physical Folders

Symptom: some images on the site no longer load, old URLs lead nowhere, thumbnails disappeared, or different image sizes now show different files.

Possible cause: physical folders move files and replace paths in the database. The replacement may not have covered some tables, relative links, builder data, or third-party fields. The mode also has compatibility limitations.

What to check: restore a staging copy or use a backup for comparison, review the mode's debug logs, see which URLs were replaced, and open different kinds of pages: posts, products, landing pages, widgets, and galleries.

How to fix it: if the issue is serious on the live site, roll back from backup. Do not try to drag files around manually over FTP without a plan. On the next attempt, enable physical folders only on staging, with selected tables and a clear validation plan.

Cloud Sync Hangs or Runs Too Long

Symptom: cloud synchronization never finishes, files appear only partially, or the admin area becomes slow.

Possible cause: a large file volume, a weak server, cloud service limits, the wrong queue method, a cron conflict, or synchronization running too frequently. The documentation describes JoomUnited Queue settings and the ability to regulate the speed of background tasks.

What to check: start with a small folder, then verify the sync method, frequency, queue state, cloud authorization errors, and server limits. Do not launch a full sync of a huge archive on a production site during peak traffic.

How to fix it: reduce the volume of the first sync, tune the queue, use cron only if you understand the infrastructure, check the cloud connection, and run the test again. If the problem keeps recurring, temporarily disable automatic synchronization and work with the developer's support team using the logs.

Safe Improvements Without Editing the Plugin Core

With WP Media Folder, there is no reason to invent snippets that interfere with its internal classes or hooks unless you truly need to. The official developer documentation includes helpers and hooks for developers, but on a normal website it is safer to start with settings, roles, folder structure, and CSS for the public-facing gallery output. You should never edit WordPress core, your theme, or plugin files directly, because updates will overwrite those changes and may introduce conflicts.

Careful CSS for Galleries

If a folder-based gallery looks too cramped in your theme, you can add a small CSS adjustment in a child theme or in a safe custom CSS tool. Before that, inspect the actual wrapper class in the browser, because the theme and block may add their own classes. The example below does not depend on internal PHP functions and only changes spacing and captions inside a container to which you manually add the wpmf-guide-gallery class in the block or section editor.

.wpmf-guide-gallery figure {
  margin-bottom: 18px;
}

.wpmf-guide-gallery figcaption {
  font-size: 14px;
  line-height: 1.45;
  color: #4b5563;
}

.wpmf-guide-gallery img {
  border-radius: 6px;
}

The validation is simple: open the page with the gallery on desktop and mobile, make sure captions are readable, images are not stretched, and the lightbox still works. The rollback is just as simple: remove the CSS or remove the wpmf-guide-gallery class from the block. This approach does not change media library data and does not depend on private plugin functions.

An Editorial Checklist Instead of Code

The best improvement for WP Media Folder is often not code at all. Create an internal checklist for your team: where product images should be uploaded, how PDFs should be named, when a file should be assigned to multiple folders, who is allowed to delete folders, when to use replace, and who approves watermarking. You can keep that checklist in site documentation or in a pinned post for editors. In practice, it prevents errors better than a complicated snippet.

When WP Media Folder Is the Right Choice

WP Media Folder is worth using when the media library is already slowing the team down or is about to become a bottleneck. The plugin helps you build a clear folder structure, filter files quickly, assign media to multiple contexts, create galleries from folders, control editor permissions, replace files without manually editing dozens of pages, and connect more advanced cloud or server workflows when needed.

Do not start with the most powerful modes. A good implementation sequence looks like this: backup, test folder, basic structure, filters, validation through a real page insertion, team training, then galleries and access permissions, and only after that cloud sync, server sync, or physical folders. That approach reduces risk and gives the team a fast result without unnecessary chaos.

If you already understand which folders you need, who will upload files, and which workflows to test after installation, you can download the ZIP archive and test the plugin on a site copy or in a safe working environment. After testing, keep only the features that actually help editors instead of making the media library more complicated for the sake of a long feature list.

The main selection criterion is simple: after setup, the editor should find files faster, upload duplicates less often, update images more confidently, and know exactly where to verify the result. If WP Media Folder gives you that on your site, it becomes more than just a media plugin - it becomes part of a healthy editorial workflow.