{"id":983,"date":"2026-09-28T10:45:22","date_gmt":"2026-09-28T10:45:22","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=983"},"modified":"2026-09-28T09:21:40","modified_gmt":"2026-09-28T09:21:40","slug":"how-to-increase-wordpress-upload-limit","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/en\/how-to-increase-wordpress-upload-limit\/","title":{"rendered":"How to Increase the WordPress Upload Limit"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">Quick Summary &#8211; WordPress Upload Limit<\/p>\n<p>WordPress uploads pass through several layers. Find the lowest active value, change only what the site needs, and verify the result from the web-facing PHP configuration.<\/p>\n<ul>\n<li><strong>Read the error<\/strong> \u2014 A WordPress size warning and an Nginx 413 response usually point to different layers.<\/li>\n<li><strong>Compare PHP values<\/strong> \u2014 Keep post_max_size above upload_max_filesize so the request has room for form data.<\/li>\n<li><strong>Check Nginx<\/strong> \u2014 Raise client_max_body_size when Nginx rejects the request before PHP.<\/li>\n<li><strong>Reload services<\/strong> \u2014 Reload PHP-FPM or Apache and Nginx after changing their configuration.<\/li>\n<li><strong>Separate memory<\/strong> \u2014 A larger upload limit does not automatically provide more PHP memory.<\/li>\n<li><strong>Keep it practical<\/strong> \u2014 Choose a limit based on the largest real file instead of setting an unnecessarily high value.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">To increase the WordPress upload limit, first identify which layer is rejecting the file: PHP, Nginx, Apache, a proxy, or the hosting panel. Raise the lowest active setting, reload the service that owns it, and verify the result from WordPress instead of trusting the configuration file you happened to edit.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>Table of Contents<\/strong><span class=\"aiw-toc-meta\"> \u00b7 11 min read<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#why-does-the-wordpress-upload-limit-look-so-low\">Why does the WordPress upload limit look so low?<\/a><\/li>\n<li><a href=\"#how-do-you-check-the-wordpress-upload-limit\">How do you check the WordPress upload limit?<\/a><\/li>\n<li><a href=\"#changing-the-php-limits\">Changing the PHP limits<\/a><\/li>\n<li><a href=\"#fixing-a-413-error-with-nginx\">Fixing a 413 error with Nginx<\/a><\/li>\n<li><a href=\"#apache-htaccess-and-hosting-panel-settings\">Apache, .htaccess, and hosting-panel settings<\/a><\/li>\n<li><a href=\"#upload-size-and-memory-are-different-limits\">Upload size and memory are different limits<\/a><\/li>\n<li><a href=\"#why-did-the-change-have-no-effect\">Why did the change have no effect?<\/a><\/li>\n<li><a href=\"#is-a-high-upload-limit-safe\">Is a high upload limit safe?<\/a><\/li>\n<li><a href=\"#check-these-before-raising-the-limit\">Check These Before Raising the Limit<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently Asked Questions<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"why-does-the-wordpress-upload-limit-look-so-low\">Why does the WordPress upload limit look so low?<\/h2>\n<p>WordPress does not get its upload limit from one switch. PHP&#8217;s <code>upload_max_filesize<\/code> and <code>post_max_size<\/code>, Nginx&#8217;s <code>client_max_body_size<\/code>, WordPress memory settings, a proxy, and sometimes the hosting panel can all affect the same request. The lowest active limit wins.<\/p>\n<p>The error usually tells you which layer to inspect first. WordPress&#8217;s &#8220;The uploaded file exceeds the upload_max_filesize directive in php.ini&#8221; message commonly points to PHP or WordPress settings. An Nginx <code>413 Request Entity Too Large<\/code> response means Nginx rejected the request before PHP received it.<\/p>\n<table>\n<thead>\n<tr>\n<th>Setting<\/th>\n<th>What it controls<\/th>\n<th>Where to check<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>upload_max_filesize<\/code><\/td>\n<td>Maximum size of one uploaded file<\/td>\n<td>PHP<\/td>\n<\/tr>\n<tr>\n<td><code>post_max_size<\/code><\/td>\n<td>Total size of a POST request<\/td>\n<td>PHP<\/td>\n<\/tr>\n<tr>\n<td><code>client_max_body_size<\/code><\/td>\n<td>Maximum Nginx request-body size<\/td>\n<td>Nginx<\/td>\n<\/tr>\n<tr>\n<td><code>memory_limit<\/code><\/td>\n<td>Memory available to a PHP process<\/td>\n<td>PHP and WordPress<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Start here:<\/strong> identify the exact error, check the values used by the web request, and raise only the lowest relevant limit. Changing every setting blindly makes the next failure harder to find.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Caution<\/p>\n<p>Do not leave phpinfo files publicly accessible. They expose PHP versions, modules, paths, and configuration details that an attacker does not need to see.<\/p>\n<\/div>\n<h2 id=\"how-do-you-check-the-wordpress-upload-limit\">How do you check the WordPress upload limit?<\/h2>\n<p>Open <em>Media &gt; Add New<\/em> in the WordPress dashboard. WordPress displays the maximum permitted file size there. WooCommerce and form plugins may have separate upload fields, so check those screens as well.<\/p>\n<p>With SSH access, first see which configuration the command-line PHP uses:<\/p>\n<pre><code>php --ini\nphp -i | grep -E 'upload_max_filesize|post_max_size|memory_limit'<\/code><\/pre>\n<p>This is CLI PHP only. A site served through PHP-FPM may use a different PHP version and a different <code>php.ini<\/code>. That distinction caught me once: I edited the CLI configuration, ran the checks, and wondered why WordPress had not changed at all.<\/p>\n<p>To inspect the web-facing PHP configuration, you can temporarily create a file such as:<\/p>\n<pre><code>&lt;?php\nphpinfo();<\/code><\/pre>\n<p>Put it in the document root as <code>info.php<\/code>, open it in a browser, and find the <code>Loaded Configuration File<\/code> line. The page also exposes PHP versions, modules, paths, and configuration details. Delete the file immediately after checking it.<\/p>\n<p>PHP&#8217;s documentation specifies that <code>post_max_size<\/code> includes uploaded files and the other form data in the request. If <code>upload_max_filesize<\/code> is 128M but <code>post_max_size<\/code> is 32M, the 128M file cannot be uploaded.<\/p>\n<p><strong>Check three views:<\/strong> the WordPress dashboard, command-line PHP, and the PHP-FPM configuration used by the website. They are not guaranteed to match.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">From the field<\/p>\n<p>I once edited the CLI PHP configuration, ran the usual checks, and saw no change in WordPress. The site was using PHP-FPM with another php.ini; checking Loaded Configuration File in a temporary phpinfo page showed me exactly where I had gone wrong. I deleted the file immediately afterward.<\/p>\n<\/div>\n<h2 id=\"changing-the-php-limits\">Changing the PHP limits<\/h2>\n<p>On a VPS, the lasting fix is to edit the <code>php.ini<\/code> file belonging to the PHP version and service that handle the site. Paths vary by distribution and PHP version. On Ubuntu with PHP 8.2 and PHP-FPM, a common path is:<\/p>\n<pre><code>\/etc\/php\/8.2\/fpm\/php.ini<\/code><\/pre>\n<p>Use values that match the actual workflow:<\/p>\n<pre><code>file_uploads = On\nupload_max_filesize = 128M\npost_max_size = 136M\nmemory_limit = 256M\nmax_execution_time = 300\nmax_input_time = 300<\/code><\/pre>\n<p>Keeping <code>post_max_size<\/code> slightly above <code>upload_max_filesize<\/code> leaves room for the rest of the form data. For one 128M file, 136M is a reasonable starting point. Several files need a larger total.<\/p>\n<p><code>memory_limit<\/code> is not the size limit for a file on disk. It limits the memory PHP can use while WordPress creates thumbnails, processes images, or runs plugin code. Raising it for every site can become expensive when many PHP-FPM workers are active.<\/p>\n<p>Reload the service after saving the file:<\/p>\n<pre><code>sudo systemctl reload php8.2-fpm\nsudo systemctl reload nginx<\/code><\/pre>\n<p>Your unit may have another name. Confirm it with <code>systemctl status php8.2-fpm<\/code>. An Apache site using mod_php may need an Apache reload instead of a PHP-FPM reload.<\/p>\n<p>Read the new value in WordPress after the reload. Do not trust the file you edited until the web request sees it.<\/p>\n<h2 id=\"fixing-a-413-error-with-nginx\">Fixing a 413 error with Nginx<\/h2>\n<p>Nginx can reject an upload before PHP sees it. Its documented default for <code>client_max_body_size<\/code> is 1 MB, which is enough to surprise anyone uploading a large theme or media file.<\/p>\n<p>Add the directive inside the relevant <code>server<\/code> block:<\/p>\n<pre><code>server {\n    server_name example.com www.example.com;\n    client_max_body_size 128M;\n\n    # Other site settings\n}<\/code><\/pre>\n<p>The virtual host is often stored at <code>\/etc\/nginx\/sites-available\/example.com<\/code> and enabled through <code>sites-enabled<\/code>. Test the configuration before applying it:<\/p>\n<pre><code>sudo nginx -t\nsudo systemctl reload nginx<\/code><\/pre>\n<p>Wait for <code>syntax is ok<\/code> and <code>test is successful<\/code>. A reload is preferable to a restart for this change because it applies the new configuration while allowing existing connections to finish where possible.<\/p>\n<p>If PHP allows 128M but Nginx allows 64M, the practical limit is 64M. The reverse can happen too. A reverse proxy, WAF, or CDN in front of Nginx may impose another limit, so inspect that layer when the local configuration looks correct.<\/p>\n<p>For a 413 response, check <code>client_max_body_size<\/code> and the Nginx error log first.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">Tip<\/p>\n<p>Run nginx -t before reloading Nginx. This small check has saved me from turning a simple upload-limit change into an avoidable outage.<\/p>\n<\/div>\n<h2 id=\"apache-htaccess-and-hosting-panel-settings\">Apache, .htaccess, and hosting-panel settings<\/h2>\n<p>Apache and PHP behave differently depending on how the stack is connected. With Apache and mod_php, these directives may work in <code>.htaccess<\/code>:<\/p>\n<pre><code>php_value upload_max_filesize 128M\nphp_value post_max_size 136M\nphp_value memory_limit 256M\nphp_value max_execution_time 300\nphp_value max_input_time 300<\/code><\/pre>\n<p>They may not work with PHP-FPM or CGI. In the wrong setup, they can cause a 500 response. Remove the lines and inspect the Apache error log if that happens.<\/p>\n<p>In cPanel and Plesk, values such as <code>upload_max_filesize<\/code>, <code>post_max_size<\/code>, and <code>memory_limit<\/code> can usually be changed through the interface. Check that the selected PHP version is the one the website actually uses. The management differences discussed in <a href=\"https:\/\/www.vps.tc\/blog\/en\/cpanel-vs-plesk-which-hosting-control-panel-is-better\/\">cPanel vs Plesk: Which Hosting Control Panel Is Better?<\/a> are relevant here.<\/p>\n<p>Some shared hosting plans prevent customers from changing these values. If edits to <code>php.ini<\/code>, <code>.user.ini<\/code>, or <code>.htaccess<\/code> do nothing, the provider&#8217;s package limit may be taking precedence. Ask support for the highest permitted values instead of repeatedly changing the same file.<\/p>\n<p>For PHP installations that use <code>.user.ini<\/code>, an example is:<\/p>\n<pre><code>upload_max_filesize=128M\npost_max_size=136M\nmemory_limit=256M<\/code><\/pre>\n<p>PHP may reread <code>.user.ini<\/code> files only at intervals. A delayed change can be normal, especially when PHP-FPM or a hosting-panel layer is involved.<\/p>\n<h2 id=\"upload-size-and-memory-are-different-limits\">Upload size and memory are different limits<\/h2>\n<p>No, they are not the same. The upload limit controls the size of an HTTP request. The WordPress memory limit controls how much RAM PHP can use while processing it. A large ZIP may mainly need disk space and enough request time; resizing a high-resolution JPEG can require much more memory.<\/p>\n<p>You can add these constants to <code>wp-config.php<\/code>:<\/p>\n<pre><code>define( 'WP_MEMORY_LIMIT', '256M' );\ndefine( 'WP_MAX_MEMORY_LIMIT', '512M' );<\/code><\/pre>\n<p><code>WP_MEMORY_LIMIT<\/code> applies to normal site operations, while <code>WP_MAX_MEMORY_LIMIT<\/code> is used by the administration area and some heavier tasks. If PHP&#8217;s <code>memory_limit<\/code> is lower, WordPress cannot exceed it. Editing only <code>wp-config.php<\/code> will not solve every memory error.<\/p>\n<p>If you see <code>Allowed memory size exhausted<\/code>, inspect PHP memory, PHP-FPM worker counts, image processing, and plugins. The separate troubleshooting steps in <a href=\"https:\/\/www.vps.tc\/blog\/en\/how-to-fix-wordpress-memory-limit-error\/\">How to Fix the WordPress Memory Limit Error<\/a> are useful here.<\/p>\n<p>Treat upload size and PHP memory as separate measurements. Increasing one does not automatically increase the other.<\/p>\n<h2 id=\"why-did-the-change-have-no-effect\">Why did the change have no effect?<\/h2>\n<p>The usual culprit is the wrong PHP version. PHP 8.1 and 8.2 may both be installed while the Nginx site uses PHP 8.2-FPM and you edited the PHP 8.1 file. Check the socket configured for the site:<\/p>\n<pre><code>grep -R \"fastcgi_pass\" \/etc\/nginx\/sites-enabled\/\nps aux | grep '[p]hp-fpm'<\/code><\/pre>\n<p>The second command avoids matching its own <code>grep<\/code> process. Small detail, but it makes the output less confusing.<\/p>\n<p>A lower layer may also be overriding the value. If Nginx allows 32M and PHP allows 128M, WordPress still cannot receive a file larger than 32M. A CDN, reverse proxy, firewall, or hosting panel can stop the request earlier.<\/p>\n<p>Check service reloads and caches too. PHP-FPM may still have old workers, Apache may still be running old processes, or the panel may not have applied the setting. Write down the value shown in WordPress before and after the change. Measure it.<\/p>\n<p>Check disk space in both the temporary upload directory and the WordPress uploads directory:<\/p>\n<pre><code>df -h\nsudo du -sh \/tmp \/var\/www\/example.com\/wp-content\/uploads<\/code><\/pre>\n<p>Permission problems produce different symptoms. If the web-server user cannot write to the destination, increasing the upload limit will not help. Changing the directory to <code>chmod 777<\/code> only hides the real problem and weakens the permissions.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">Example<\/p>\n<p>If PHP allows 128M but Nginx allows 64M, the effective WordPress upload limit is 64M. If a CDN allows only 32M, the CDN becomes the limiting layer instead.<\/p>\n<\/div>\n<h2 id=\"is-a-high-upload-limit-safe\">Is a high upload limit safe?<\/h2>\n<p>A value such as 128M or 512M is not automatically a vulnerability, but it permits larger requests and can consume more resources. Allow only the file types the site needs, protect administrator accounts with multifactor authentication, and prevent executable scripts from running in the upload directory.<\/p>\n<p>Unnecessarily high <code>max_execution_time<\/code> and <code>max_input_time<\/code> values can keep PHP workers busy during slow uploads. On a small VPS, watch CPU, RAM, disk I\/O, and PHP-FPM processes while testing concurrent uploads.<\/p>\n<p>A CDN can improve media delivery, but it does not remove the origin upload limit. The application still has to accept the request. For the surrounding setup, see <a href=\"https:\/\/www.vps.tc\/blog\/en\/install-wordpress-on-vps-step-by-step\/\">How to Install WordPress on a VPS: Step-by-Step Guide<\/a>, <a href=\"https:\/\/www.vps.tc\/blog\/en\/install-configure-nginx-on-ubuntu\/\">How to Install and Configure Nginx on Ubuntu<\/a>, and <a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-a-cdn-how-it-speeds-up-websites\/\">What Is a CDN? How It Speeds Up Websites<\/a>.<\/p>\n<p>Set the limit slightly above the largest file users genuinely need, then watch the logs during one real upload. That final test is worth more than another round of guessing.<\/p>\n<h2 id=\"check-these-before-raising-the-limit\">Check These Before Raising the Limit<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Read the exact WordPress or web-server error.<\/li>\n<li>Check the active PHP-FPM version and configuration file.<\/li>\n<li>Set post_max_size above upload_max_filesize when form data needs room.<\/li>\n<li>Raise client_max_body_size when Nginx handles the site.<\/li>\n<li>Reload the relevant PHP and web-server services.<\/li>\n<li>Confirm the new value in the WordPress Media screen.<\/li>\n<li>Check disk space, permissions, logs, and resource use during a large upload.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Set the WordPress upload limit around the largest file your users genuinely need, then test one real upload while watching the PHP-FPM and web-server logs. That final verification is worth more than another round of guessing.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/en\/vps\">Explore VPS plans<\/a><\/p>\n<\/div>\n<h2 id=\"frequently-asked-questions\">Frequently Asked Questions<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>What is the default WordPress upload limit?<\/summary>\n<p>There is no single WordPress-wide default. The displayed limit comes mainly from the active PHP configuration and can also be constrained by Nginx, Apache, a proxy, or the hosting provider. Shared hosting packages often impose their own maximum. Check Media &gt; Add New in WordPress, then compare that value with the PHP-FPM configuration used by the website.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Why does WordPress still show a low upload limit after editing php.ini?<\/summary>\n<p>You may have edited the wrong php.ini. CLI PHP, PHP-FPM, Apache, and different PHP versions can use separate configuration files. Check the website&#039;s PHP-FPM socket and verify Loaded Configuration File through a temporary phpinfo page. Reload the relevant service afterward, and remove the phpinfo file when finished.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>What should post_max_size be for a 128M upload?<\/summary>\n<p>Set post_max_size slightly higher than upload_max_filesize so the request has room for form fields and other POST data. A value of 136M is a reasonable starting point for one 128M file, but several files require a larger total. The practical limit is still the lowest value enforced by PHP, Nginx, a proxy, or the hosting panel.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>How do I fix the Nginx 413 Request Entity Too Large error?<\/summary>\n<p>Add or raise client_max_body_size in the relevant Nginx server block, for example to 128M. Run nginx -t and confirm both syntax is ok and test is successful before reloading Nginx. If the error remains, inspect reverse proxies, CDNs, firewalls, and the Nginx error log because another layer may have its own request-size limit.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Does increasing the upload limit require more WordPress memory?<\/summary>\n<p>Not always. A large ZIP may mainly require disk space and enough request time, while image resizing can require substantial PHP memory. Keep upload size and memory_limit separate. If WordPress reports Allowed memory size exhausted, inspect PHP memory, worker counts, image processing, and plugins instead of raising the upload limit alone.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Is it safe to set the WordPress upload limit to 512M?<\/summary>\n<p>A 512M limit is not automatically unsafe, but it permits larger requests that consume more disk, CPU, RAM, and PHP worker time. Allow only the file types the site needs, protect administrator accounts with multifactor authentication, prevent script execution in uploads, and monitor logs and resources. Choose the smallest limit that supports the real workflow.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"sources\">Sources<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/www.php.net\/manual\/en\/ini.core.php\" target=\"_blank\" rel=\"noopener\">PHP Manual &#8211; Core php.ini Directives<\/a> \u2014 php.net<\/li>\n<li><a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_core_module.html\" target=\"_blank\" rel=\"noopener\">Nginx Documentation &#8211; Core Module<\/a> \u2014 nginx.org<\/li>\n<li><a href=\"https:\/\/wordpress.org\/documentation\/article\/editing-wp-config-php\/\" target=\"_blank\" rel=\"noopener\">WordPress Documentation &#8211; Editing wp-config.php<\/a> \u2014 wordpress.org<\/li>\n<li><a href=\"https:\/\/www.php.net\/manual\/en\/configuration.file.per-user.php\" target=\"_blank\" rel=\"noopener\">PHP Manual &#8211; User INI Files<\/a> \u2014 php.net<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Increase the WordPress upload limit by checking PHP, Nginx, Apache, hosting-panel, and memory settings in the right order.<\/p>\n","protected":false},"author":2,"featured_media":981,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-983","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cmss"],"lang":"en","translations":{"en":983,"tr":982},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/983","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=983"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/983\/revisions"}],"predecessor-version":[{"id":985,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/983\/revisions\/985"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/981"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=983"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=983"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=983"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}