{"id":49330,"date":"2025-05-14T04:34:22","date_gmt":"2025-05-14T04:34:22","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=49330"},"modified":"2025-05-14T04:34:22","modified_gmt":"2025-05-14T04:34:22","slug":"increasing-the-maximum-image-upload-size-on-a-wordpress-site","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/increasing-the-maximum-image-upload-size-on-a-wordpress-site\/","title":{"rendered":"Increasing the Maximum Image Upload Size on a WordPress Site"},"content":{"rendered":"\n

Increasing the upload file size limit in WordPress allows you to upload larger images (or other media) without errors. Many hosting providers set a default upload limit (often anywhere from 2 MB to 500 MB) at the server level. If you try to upload a file larger than this limit, WordPress will show an error such as \u201cthe uploaded file exceeds the upload_max_filesize directive in php.ini\u201d<\/em>. In this guide, we\u2019ll walk through several methods to raise the upload size limit on a WordPress site hosted on cPanel. We will cover editing the .htaccess<\/code><\/strong>, php.ini<\/code><\/strong>, and wp-config.php<\/code><\/strong> files, explain how to locate or create each file via cPanel\u2019s File Manager, and discuss best practices, potential conflicts on shared hosting, and fallback options (like using a plugin or contacting your host).<\/p>\n\n\n\n

Note:<\/strong> Before making any changes, it\u2019s wise to back up your site and these configuration files<\/strong>. A small typo in .htaccess<\/code> or wp-config.php<\/code> can cause site errors, so having a backup lets you revert if needed. Also, try one method at a time<\/strong> \u2013 you usually don\u2019t need to apply all methods, and using multiple methods simultaneously might lead to conflicting settings.<\/p>\n\n\n\n

1. Checking Your Current Upload Limit<\/h2>\n\n\n\n

Before changing anything, check what your site\u2019s current upload size limit is. In your WordPress admin dashboard, go to Media \u00bb Add New<\/strong>. At the bottom of the upload screen, WordPress displays the \u201cMaximum upload file size\u201d<\/strong> allowed (e.g. \u201cMaximum upload file size: 2 MB\u201d). You can also find this info under Tools \u00bb Site Health \u00bb Info \u00bb Media Handling<\/strong> or Server<\/strong> sections (look for \u201cMax size of an uploaded file\u201d<\/em> or \u201cupload_max_filesize\u201d<\/em>). Knowing the current limit will confirm if your changes work later.<\/p>\n\n\n\n

If you\u2019ve already encountered an error while uploading, WordPress likely told you the file exceeded a certain size. Make note of that size (e.g. 2 MB, 16 MB, etc.) so you know what the old limit is.<\/p>\n\n\n\n

2. Method 1: Increasing Upload Size via .htaccess<\/code><\/h2>\n\n\n\n

The .htaccess<\/code> file is an Apache configuration file that WordPress uses (on Apache\/LiteSpeed servers) for things like permalinks. You can also add PHP directives here to increase upload limits, if<\/strong> your server allows it. This method works on many cPanel hosts, but note that if your host runs PHP in CGI\/FastCGI mode (common in shared hosting), using php_value<\/code> directives in .htaccess<\/code> may cause a 500 Internal Server Error<\/strong>. We\u2019ll address what to do in that case shortly.<\/p>\n\n\n\n

Steps to edit .htaccess:<\/strong><\/p>\n\n\n\n

    \n
  1. Open cPanel File Manager and locate your site\u2019s root folder.<\/strong> Log in to cPanel and click File Manager<\/strong> (usually under the \u201cFiles\u201d section). Navigate to your site\u2019s document root directory \u2013 for a primary domain, this is often the public_html<\/strong> folder. If WordPress is in a subfolder or addon domain, go to that folder.<\/li>\n\n\n\n
  2. Enable view of hidden files (dotfiles).<\/strong> The .htaccess<\/code> filename begins with a dot, so it\u2019s hidden by default. In File Manager, click the Settings<\/strong> button (typically top-right) and check \u201cShow Hidden Files (dotfiles)\u201d<\/strong>, then click Save. This will reveal files like .htaccess<\/code> that were previously invisible. If you don\u2019t see a Settings button, your host\u2019s File Manager might show a prompt to display hidden files when you open it. Make sure this option is enabled. In cPanel\u2019s File Manager preferences, enable \u201cShow Hidden Files (dotfiles)\u201d to ensure you can see the .htaccess<\/code> file. By default, files beginning with a dot are hidden, so this setting must be checked. Once enabled, any hidden files (like .htaccess<\/code>) will become visible in the directory listing.<\/em><\/li>\n\n\n\n
  3. Find the .htaccess<\/code> file in the root folder.<\/strong> With hidden files now visible, look for .htaccess<\/strong> in the public_html (or your WordPress root) directory. If your WordPress permalinks are working, this file likely already exists. You should see it listed alongside files like wp-config.php<\/code> and folders like wp-content<\/code>, etc. The .htaccess<\/code> file as shown in the public_html directory (highlighted). If this file is missing, you can create a new one via the \u201c+ File\u201d option in File Manager. Ensure you name it exactly .htaccess<\/code> (with the dot at the beginning).<\/em><\/li>\n\n\n\n
  4. Edit the .htaccess<\/code> file.<\/strong> Right-click on .htaccess<\/code> and choose Edit<\/strong> (or Code Edit<\/strong>). If prompted for character encoding, you can proceed with default (usually UTF-8). Be careful not to remove existing WordPress rules<\/strong> in this file. Scroll to the bottom (or find a suitable place) and add the following lines: php_value upload_max_filesize 128M php_value post_max_size 128M php_value max_execution_time 300 php_value max_input_time 300<\/code> These lines increase the PHP limits when your site runs under Apache:
    • php_value upload_max_filesize 128M<\/code> \u2013 sets the maximum size of an uploaded single file to 128 megabytes<\/strong>. You can adjust this number as needed (e.g. 64M<\/code>, 256M<\/code>, etc.).<\/li>
    • php_value post_max_size 128M<\/code> \u2013 sets the maximum size of POST data to 128 MB. This must be equal or larger<\/strong> than upload_max_filesize<\/code>. It defines the total size of the request (file + form data) that PHP will accept.<\/li>
    • php_value max_execution_time 300<\/code> \u2013 increases the script execution time to 300 seconds<\/strong> (5 minutes). This helps prevent timeout errors when uploading or processing a large file.<\/li>
    • php_value max_input_time 300<\/code> \u2013 increases the time PHP will spend parsing input (such as a file upload) to 300 seconds. Similarly, this is to prevent timeouts for big uploads.<\/li><\/ul>Save the changes to .htaccess<\/code>.<\/li>\n\n\n\n
    • Test the new limit.<\/strong> In WordPress, go back to Media \u00bb Add New<\/strong>. The maximum upload size displayed should now reflect the new value (around 128 MB in this example). Try uploading a file larger than the old limit but smaller than the new limit to confirm the change. If it uploads successfully, the method worked. If you still see the old limit or get an error, we will try another method below.<\/li>\n<\/ol>\n\n\n\n

      Potential issues:<\/strong> If after adding those lines your site starts throwing a 500 Internal Server Error<\/strong>, it likely means your server does not allow PHP overrides in .htaccess<\/code> (common when PHP runs as CGI\/FastCGI rather than an Apache module). In that case, you should remove those lines<\/strong> (restore the .htaccess<\/code> to its previous state) to get your site working again, and use one of the methods below instead. Some hosts also disable using .htaccess<\/code> for PHP settings altogether on certain plans. Don\u2019t worry \u2013 you can achieve the same result with a php.ini<\/code> or wp-config.php<\/code> change.<\/p>\n\n\n\n

      3. Method 2: Increasing Upload Size via php.ini<\/code> (or .user.ini<\/code>)<\/h2>\n\n\n\n

      PHP\u2019s main configuration is controlled by a php.ini<\/strong> file. On many cPanel hosts, you can create a custom php.ini in your account to override specific settings like upload size. In modern cPanel environments with PHP-FPM, you might instead use a file named .user.ini<\/code> for per-directory PHP settings (the syntax is the same as php.ini). We will describe using php.ini<\/strong>, but check with your host documentation if .user.ini<\/code> is required. (If your host uses cPanel\u2019s MultiPHP INI Editor<\/strong>, that tool is effectively editing your php.ini for you \u2013 we\u2019ll note that in a moment.)<\/p>\n\n\n\n

      Steps to edit or create php.ini:<\/strong><\/p>\n\n\n\n

        \n
      1. Locate the php.ini file (if it exists).<\/strong> In cPanel\u2019s File Manager, still in your site\u2019s root folder (public_html), see if a file named php.ini<\/strong> already exists. It may or may not be present on shared hosting. Commonly, if you have used cPanel\u2019s PHP editors or your host provided one, it might be there. If you find php.ini<\/code>, right-click and choose Edit.<\/li>\n\n\n\n
      2. If no php.ini is found, create one.<\/strong> If you don\u2019t see a php.ini, you can create a new file in the root folder named php.ini<\/strong> (or use the + File<\/strong> button to create it). In some cases, the host might require naming it .user.ini<\/strong> \u2013 you can create that as well, but usually cPanel with PHP versions >7 will recognize php.ini in the root for custom settings. (Alternatively, some hosts have a \u201cMultiPHP INI Editor\u201d<\/strong> in cPanel that lets you set PHP values without manually editing files. Using that GUI will achieve the same outcome by updating your php.ini behind the scenes. If you prefer, you can use that tool by selecting your domain and then changing upload_max_filesize<\/em> and post_max_size<\/em> there.)<\/li>\n\n\n\n
      3. Edit php.ini to add upload size directives.<\/strong> Open the php.ini file (newly created or existing) and add the following lines (or modify them if they already exist): upload_max_filesize = 128M post_max_size = 128M memory_limit = 256M max_execution_time = 300 max_input_time = 300<\/code> Explanation of these settings:
        • upload_max_filesize = 128M<\/strong> \u2013 sets the upload limit per file to 128 MB (same as in the .htaccess method). Change \u201c128M\u201d to your desired file size limit.<\/li>
        • post_max_size = 128M<\/strong> \u2013 allows POST requests up to 128 MB. This must be at least as large as upload_max_filesize<\/code>. If you set one to 256M and not the other, the smaller one will bottleneck your uploads.<\/li>
        • memory_limit = 256M<\/strong> \u2013 (Optional but recommended) increases PHP memory available. When handling large uploads or image processing, more memory may be needed. We set it to 256 MB here, but you can adjust as needed. Ensure this value is equal or greater than the file size you set, especially if you\u2019ll be manipulating images or other memory-intensive operations.<\/li>
        • max_execution_time = 300<\/strong> \u2013 increases script time limit to 300 seconds. This pairs with the above to ensure the script can run long enough for big uploads.<\/li>
        • max_input_time = 300<\/strong> \u2013 increases input parsing time to 300 seconds, for the same reason.<\/li><\/ul>Save the php.ini file.<\/li>\n\n\n\n
        • Verify the changes.<\/strong> It\u2019s a good idea to double-check that your new values are actually being applied. One way is to create a PHP info file: using File Manager, create a new file (e.g. info.php<\/code>) in public_html with the content <?php phpinfo(); ?><\/code>. Visit this file in your browser (e.g. https:\/\/yourdomain.com\/info.php<\/code>) and look for upload_max_filesize<\/em> and post_max_size<\/em> values in the output. They should show \u201c128M\u201d (or your set value). You can delete the info.php file afterward. Alternatively, in WordPress, go to Tools \u00bb Site Health \u00bb Info \u00bb Server<\/strong> and confirm the \u201cUpload max filesize\u201d reflects the new value.<\/li>\n\n\n\n
        • Test uploading a file.<\/strong> Again, try uploading a file via Media library that\u2019s larger than the old limit and under the new limit. If it works without error and the limit displayed is higher, the php.ini method was successful. WordPress should now allow images (and other files) up to the size you configured.<\/li>\n<\/ol>\n\n\n\n

          Important:<\/strong> On shared hosting<\/strong>, some providers do not allow custom php.ini<\/strong> changes or they cap the maximum you can set. Hostinger, for example, notes that many shared hosts won\u2019t allow editing php.ini directly and you should confirm with support if you can modify it. If you find that even after editing php.ini the limits don\u2019t change, the host might be ignoring your php.ini (or requiring a different file like .user.ini). In that case, contacting the host support or using their provided interface (like MultiPHP INI Editor) is recommended. Additionally, keep your php.ini in the correct directory \u2013 if WordPress is in a subfolder, the php.ini might need to be placed there or in the home directory<\/strong>, depending on how the host loads configurations. Check your host\u2019s knowledge base for \u201ccustom php.ini\u201d instructions if unsure.<\/p>\n\n\n\n

          4. Method 3: Increasing Upload Size via wp-config.php<\/code><\/h2>\n\n\n\n

          Another approach is to apply settings in WordPress\u2019s configuration file wp-config.php<\/strong>. This file resides in the root of your WordPress installation and controls many aspects of WordPress. By adding some PHP directives here, you might increase the upload limits. However, note that this method is not always effective for upload size limits \u2013 because the server may evaluate the maximum file size before<\/em> WordPress (and thus wp-config) is fully loaded. Still, it can be a useful supplement, especially for increasing memory limits, and it\u2019s easy to try since you already have access to the file.<\/p>\n\n\n\n

          Steps to edit wp-config.php:<\/strong><\/p>\n\n\n\n

            \n
          1. Locate wp-config.php in File Manager.<\/strong> In the same root folder (public_html or your WP folder), find wp-config.php<\/strong> \u2013 it should be visible (this one is not hidden). If you\u2019re in public_html, you will see wp-config.php<\/code> alongside wp-content, wp-admin, etc. Right-click wp-config.php<\/strong> and choose Edit<\/strong>.<\/li>\n\n\n\n
          2. Open the file for editing.<\/strong> When the editor opens, you will see many lines of configuration (database settings, salts, etc.). Scroll down toward the bottom of the file. Look for the line that says: \/* That's all, stop editing! Happy publishing. *\/<\/code> It\u2019s typically near the end. Above that line<\/strong>, add the following code snippet (or you can add it anywhere above the comment, but placing near the end keeps things organized): \/\/ Increase PHP upload limits @ini_set( 'upload_max_filesize' , '128M' ); @ini_set( 'post_max_size', '128M'); @ini_set( 'memory_limit', '256M' );<\/code> And optionally, you can also add: define( 'WP_MEMORY_LIMIT', '256M' );<\/code> Here\u2019s what each line does:
            • @ini_set( 'upload_max_filesize' , '128M' );<\/code> \u2013 Attempts to set the PHP upload_max_filesize to 128 MB at runtime (the @<\/code> suppresses any warning if it fails). This is the same directive we set in php.ini earlier.<\/li>
            • @ini_set( 'post_max_size' , '128M' );<\/code> \u2013 Attempts to set post_max_size to 128 MB.<\/li>
            • @ini_set( 'memory_limit' , '256M' );<\/code> \u2013 Increases the PHP memory limit for this script to 256 MB. This is similar to setting memory_limit in php.ini. We do this because WordPress may need more memory to handle large uploads or image processing.<\/li>
            • define( 'WP_MEMORY_LIMIT', '256M' );<\/code> \u2013 This is a WordPress-specific constant to bump up WordPress\u2019s internal memory limit setting. By default, WordPress might limit itself to e.g. 40M for a single site. Setting this ensures WordPress itself will allow up to 256 MB usage. (This mainly affects PHP memory for WordPress operations, which indirectly helps if large images are being resized, but it does not alone change the upload file size cap. It\u2019s a complementary setting.)<\/li><\/ul>Save the changes to wp-config.php.<\/li>\n\n\n\n
            • Test the effect.<\/strong> Because of how PHP works, the ini_set<\/code> calls in wp-config.php may not take effect early enough to permit a bigger file upload in the same request. However, it doesn\u2019t hurt to have them as a fallback. After adding, try uploading a large file again or check Site Health Info. If your host allowed the .htaccess or php.ini changes, those would already have done the job. The wp-config changes are more of a safety net. In some cases (depending on host configuration), these settings could help if the upload limit was being capped by WordPress itself rather than PHP.<\/li>\n<\/ol>\n\n\n\n

              If this method alone doesn\u2019t seem to raise the limit, rely on the .htaccess or php.ini methods above, as they work at the server configuration level. The wp-config.php<\/code> tweaks are best used in combination with those, especially to ensure memory is boosted. Always keep wp-config.php<\/code> edits minimal and double-check for syntax errors (a missing quote or semicolon could crash your site). If you encounter issues after editing, restore the backup of wp-config.php.<\/p>\n\n\n\n

              5. Best Practices and Considerations (Shared Hosting)<\/h2>\n\n\n\n

              Increasing the upload size may be straightforward, but here are some best practices and things to watch out for, especially in shared hosting environments:<\/p>\n\n\n\n

                \n
              • Match or exceed related limits:<\/strong> Always set post_max_size<\/em> >= upload_max_filesize<\/em>. If post_max_size<\/em> is smaller, your uploads will still fail or be truncated. Also, ensure memory_limit<\/em> is high enough to handle the file \u2013 it should be at least as large as upload_max_filesize<\/em> (and typically much more if you process images).<\/li>\n\n\n\n
              • PHP environment matters:<\/strong> The method that works depends on how PHP is configured on your server. If PHP is running as an Apache module (mod_php), the .htaccess<\/code> method with php_value<\/code> works well. If PHP runs as CGI\/FastCGI (e.g. PHP-FPM or suPHP, common in shared hosting), then .htaccess<\/code> cannot override PHP settings and will cause errors. In those cases, use php.ini (or .user.ini) to set values, as the PHP process will read those on start. Some hosting control panels (like cPanel) also provide a PHP Configuration<\/strong> or MultiPHP INI Editor<\/strong> to make these changes easily via a UI \u2013 consider using those to avoid syntax mistakes.<\/li>\n\n\n\n
              • Hosting-imposed limits:<\/strong> Be aware that your host may enforce an upper limit on upload file size regardless of what you set. For instance, you might set 512M, but the host\u2019s PHP config or plan might cap it at 50M or 100M. If you find you cannot increase beyond a certain point, that is likely a host restriction. \u201cStarter\u201d shared hosting plans often have lower limits than higher-tier plans. In such cases, you may need to contact the host to raise the limit (they might do so if you ask, or they might require you to upgrade plans for significantly higher limits).<\/li>\n\n\n\n
              • File creation and permissions:<\/strong> When creating new files like .htaccess<\/code> or php.ini<\/code>, ensure they have the correct filenames (no .txt<\/code> extension, for example). The File Manager should create them with proper permissions by default (usually 644 for files). If you upload a php.ini via FTP, also ensure it\u2019s in the correct directory and has suitable permissions. Incorrect permissions or ownership can sometimes cause the file to be ignored or cause errors.<\/li>\n\n\n\n
              • Keep backups of config files:<\/strong> It\u2019s worth reiterating \u2013 always save a copy of the original .htaccess<\/code> or wp-config.php<\/code> before you edit. This way, if something goes wrong, you can quickly revert. Even better, make one change at a time and test, rather than changing multiple things at once. This will help isolate if a particular change caused an issue.<\/li>\n\n\n\n
              • Avoid conflicts:<\/strong> Try to use one primary method to set the values. If you set different upload_max_filesize in .htaccess and php.ini, it could confuse you later. Typically, PHP will use whichever is loaded last (php.ini is loaded at startup, .htaccess could override at runtime if allowed). For clarity, pick one approach that works on your host. The exception is wp-config.php<\/code> where adding the settings doesn\u2019t usually conflict but may be redundant; it\u2019s mostly for completeness.<\/li>\n\n\n\n
              • WordPress Multisite note:<\/strong> If you are running a WordPress Multisite network, there is a separate network admin setting for max upload size (which defaults to 1500 KB (~1.5MB) unless changed). Increasing the PHP limits will allow higher values, but you also need to go to My Sites \u00bb Network Admin \u00bb Settings<\/strong> and increase the \u201cMax upload file size\u201d<\/em> setting for the network, otherwise site admins will still be limited by that value.<\/li>\n<\/ul>\n\n\n\n

                6. Fallback Options (Plugins or Hosting Support)<\/h2>\n\n\n\n

                If you have tried editing .htaccess<\/code>, php.ini<\/code>, and wp-config.php<\/code> and the upload limit still hasn\u2019t increased, don\u2019t despair. Here are some fallback options:<\/p>\n\n\n\n

                  \n
                • Use a WordPress plugin:<\/strong> There are plugins specifically designed to increase the upload size limit. One popular option is the \u201cWP Increase Upload Filesize\u201d<\/strong> plugin. After installing and activating such a plugin, it often provides a settings page (for example, under Media \u00bb Increase Upload Limit<\/strong>) where you can select a new maximum upload size from a dropdown. Under the hood, these plugins typically try to update the same settings we did manually (or use WordPress filters) \u2013 but they provide a user-friendly interface. Keep in mind that a plugin cannot bypass server-level restrictions; for instance, it will not allow you to set a value higher than what the server allows. In fact, WP Increase Upload Filesize will show you the maximum possible limit (based on server config) in its dropdown, and if you need more, it will advise contacting your host. Using a plugin can be convenient if you\u2019re not comfortable editing files, but since you do have cPanel access, it\u2019s essentially doing the same thing you\u2019ve attempted.<\/li>\n\n\n\n
                • Contact your hosting support:<\/strong> This is often the simplest and most reliable solution<\/strong>. Hosting providers deal with upload limit requests frequently, and it\u2019s usually a trivial change for them (especially if you are on a managed plan). Reach out to your host via phone or support ticket or chat, and ask \u201cCan you increase the PHP upload_max_filesize and post_max_size for my account? I need to upload files of X MB.\u201d<\/strong>. Specify the size you need. Many hosts will gladly increase it or tell you the maximum they can allow on your current plan. Some hosts have documentation for this; others might guide you to a specific solution for their environment (like a custom php.ini location or a control panel setting). If the host says you\u2019re at the maximum for your plan, you might consider an upgrade if it\u2019s critical for your site, or use an alternative approach (e.g., upload via FTP and then import, which sidesteps PHP upload limits).<\/li>\n\n\n\n
                • Alternative upload methods:<\/strong> As a last resort, if you cannot increase the limit and the host won\u2019t assist (or you need a one-time upload of a huge file), you could upload the file via FTP or cPanel\u2019s File Manager, placing it in wp-content\/uploads<\/code> (or a subfolder by date), and then use a plugin like \u201cAdd From Server\u201d or a custom script to import it into the WordPress Media Library. This bypasses PHP\u2019s upload size restrictions since you\u2019re not going through PHP\u2019s upload mechanism. However, this is usually unnecessary if you can get the configuration updated by using the earlier methods or your host\u2019s help.<\/li>\n<\/ul>\n\n\n\n

                  7. Conclusion<\/h2>\n\n\n\n

                  By using one or a combination of the methods above, you should be able to raise the maximum image upload size for your WordPress site on cPanel hosting. In summary, editing the PHP settings via .htaccess<\/code> or php.ini<\/code> has a server-wide effect for your site and is the most direct way, while WordPress config tweaks and plugins provide additional ways to ensure the limits are increased. Always be mindful of the environment \u2013 on shared hosts there may be caps or specific procedures to follow. Once the new limits are in place, you\u2019ll be able to upload higher-resolution images, large media files, or hefty plugins\/themes as needed. Monitor your site after making these changes to ensure it\u2019s stable, and enjoy the greater freedom in managing your media. Happy publishing!<\/p>\n\n\n\n

                  Sources<\/h3>\n\n\n\n
                    \n
                  • WPBeginner \u2013 How to Increase the Maximum File Upload Size in WordPress<\/em><\/li>\n\n\n\n
                  • Hostinger \u2013 How to Increase the Maximum Upload File Size in WordPress<\/em><\/li>\n\n\n\n
                  • cPanel Community \u2013 Viewing Hidden Files in File Manager<\/li>\n\n\n\n
                  • Reddit (r\/webdev) \u2013 php_value in .htaccess causing 500 error<\/li>\n\n\n\n
                  • PHP Manual \u2013 ini_set limitations for upload_max_filesize<\/li>\n\n\n\n
                  • IONOS \u2013 WordPress Upload Limit Tips<\/li>\n\n\n\n
                  • Kinsta \u2013 Why hosts impose upload limits<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

                    Increasing the upload file size limit in WordPress allows you to upload larger images (or other media) without errors. Many hosting providers set a default upload limit (often anywhere from… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-49330","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49330","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=49330"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49330\/revisions"}],"predecessor-version":[{"id":49331,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49330\/revisions\/49331"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=49330"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=49330"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=49330"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}