How to Restrict Access to Files within WordPress Folders

Our Prevent Direct Access (PDA) Gold plugin provides an easy way to help you protect your private files. You can either protect individual or multiple files at the same time with WordPress Bulk Actions. Now you can even protect the entire folder, i.e. all files on that folder, with PDA Access Restriction extension.


In this article, we’ll show you how to restrict access to entire WordPress folders in popular hosting servers.

Apache – Single Site

After activating our plugins successfully, navigate to Prevent Direct Access Gold >> Settings menu from your admin dashboard.

Switch to the “Folder Protection” tab and protect your private folders following the 4 steps below.

Step 1: Select folders you want to protect

  • You can only select the main folders under WordPress root or uploads directory.
  • Only folders whose name contains lowercase letters (a-z), numbers (0-9), dash (-), and underscore (_) are accepted and displayed under the Select field. If your desired folders aren’t listed here, double-check if their names follow this rule.

Step 2: Select file types

Our plugin protects all file types in protected folders by default.

However, you can choose to protect certain file types only. The other files can be accessed publicly as usual.

Step 3: Set access permission

After selecting folders and file types to protect, you need to define who can access your protected files based on:

  • User roles
    • Default value: Admin users
  • Users
    • Default value: No users

This option is applied to all protected files and sub-folders under the selected folders.

To grant different permission to different folders under the uploads directory, you need to define our custom constant in the wp-config.php file.

Step 4: Set whitelisted referrer URLs (optional)

This option allows you to define access permission based on where users come from.

Unlike how PDA Gold moves all protected files into the _pda directory, this folder protection method keeps all your file URLs unchanged.

The default WordPress media folders such as 2018 and 2019 are also displayed. So if you choose those folders, you might experience UI conflicts with PDA Gold’s default file protection in the Media library.

“No Access” Rule

If users access a protected file without permission, they will be redirected to the 404 error page or custom “No Access” page depending on your settings.

Apache – Multisite

Main site

After configuring and saving the feature options successfully, go back to the Settings tab to get the rewrite rules and copy them to your .htaccess file as per our instructions.


For our feature to work properly on subsites, simply replace the above Folder Protection rules with the following:

# AR Rewrite Rules for Folder Protection
# Root Folder Protection
RewriteRule ^((your-root-folder-name-1|your-root-folder-name-2)/.*\.\w+)$ index.php?pda_v3_pf=$1 [QSA,L] 
# Folder Protection under Uploads
RewriteRule ^wp-content/uploads(?:/sites/[0-9]+)?(/(your-folder-name-1|your-folder-name-2)/.*\.\w+)$ index.php?pda_v3_pf=$1 [QSA,L]
# AR Rewrite Rules for Folder Protection End

Please note that:

  • The root folder permission is set on the main site. It doesn’t follow subsites’ permission even if you select them under each subsite.
  • There are 2 different file URLs and permissions, even though they’re technically pointing to the same original file:
      This file URL will always return 404.
      This file URL will follow the File Access Permission you set under Site 9 – Prevent Direct Access Gold – Folder Protection tab

Rewrite Rules for WP Engine

For our feature to work on WP Engine, you have to implement these rewrite rules as follows.

For folders under Uploads Directory

Redirect name Rules for folder protection
Source wp-content/uploads(/(folder-1 | folder-2)/.*\.\w+)$
Redirect type 301 Permanent

For folders under Root Directory

Redirect name Rules for folder protection
Source (/(folder-1 | folder-2)/.*\.\w+)$
Redirect type 301 Permanent

* “folder-1” and “folder-2” are folders you want to protect. Use | to separate each folder name.

Rewrite Rules for NGINX servers

Please follow 3 simple steps below to update folder protection rules in the Nginx server:

Step 1: Copy the rewrite rules shown under Folder Protection tab

Step 2: Find and open your website’s Nginx config file which is normally located at /etc/nginx/site-available (or /etc/nginx/conf/site-available if you’re using Arch Linux)

Step 3: Put it inside the server block

server {

    location / {

   #Put our rewrite rules here, i.e.
   rewrite ((prevent-direct-access)/.*\.\w+)$ "/index.php?pda_v3_pf=$1" last;
   rewrite wp-content/uploads(/(protect\s+page\s+and\s+post)/.*\.\w+)$ "/index.php?pda_v3_pf=$1" last;

After that, restart your Nginx server. Folder Protection feature should be now working properly on your website.

Other Hosting Servers

  • Cloudways
  • LiteSpeed
  • Plesk

Some hosting providers running on Plesk – with Nginx as a reverse proxy, don’t allow users to customize Nginx rewrite rules. Besides, those using Nginx caching servers such as Cloudways and LiteSpeed will cache your files no matter how they are protected.

If that’s the case, you can still make our Folder Protection work by following the instruction below:

  1. Select specific folders that you want to protect, which could be in your WordPress root or uploads directory, under our Folder Protection settings tab.
  2. Create a .htaccess file under these folders with the following rules:
    # Apache 2.2
    <IfModule !mod_authz_core.c>
    Order Deny,Allow
    Deny from all
    # Apache 2.4
    <IfModule mod_authz_core.c>
    Require all denied

    All your files under the folders should be prevented from direct access now. For example, these 2 URLs should return 404 if users don’t have the permission set under our “Folder Protection” settings tab:

  3. Access your protected files through our raw URL instead:
Lasted updated on August 23, 2021