=== Converter for Media - Optimize images | Convert WebP & AVIF ===
Contributors: mateuszgbiorczyk
Donate link: https://url.mattplugins.com/converter-readme-donate-link
Tags: convert webp, webp, optimize images, image optimization, compress images
Requires at least: 4.9
Tested up to: 6.2
Requires PHP: 7.0
Stable tag: 5.9.3
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Speed up your website by using our WebP & AVIF Converter. Optimize images and serve WebP and AVIF images instead of standard formats!

== Description ==

**Speed up your website using our ease image optimizer by serving WebP and AVIF images.** By replacing files in standard JPEG, PNG and GIF formats with WebP and AVIF formats, you can save over a half of the page weight without losing quality.

[youtube https://www.youtube.com/watch?v=Ls2h38avpRw]

After installing the plugin you do not have to do anything more. Your current images will be converted into a new format. When image optimization by our image optimizer is finished, users will automatically receive new, much lighter images than the original ones.

As of today, over 90% of users use browsers that support the WebP format. The loading time of your website depends to a large extent on its weight and the level of image optimization. **Using our WebP Converter, now you can and speed up it in a few seconds without much effort!**

This will be a profit both for your users who will not have to download so much data, but also for a server that will be less loaded. Remember that a better optimized website also affects your Google ranking. Image optimization is very important.

#### AVIF support

Now in [the PRO version](https://url.mattplugins.com/converter-readme-avif-support-upgrade) you can use AVIF as the output format for your images. The AVIF format is a new extension - is the successor to WebP. **AVIF allows you to achieve even higher levels of image compression**, and the quality of the converted images after image optimization is better than in WebP.

#### How does this work?

- If you have just installed the plugin, you can optimize images with one click. Image size will be smaller after generate webp!
- New images that will be added to the Media Library will be converted automatically.
- Our image optimizer does not modify your original images in any way. This means security for you and your files.
- When the browser loads an image, our plugin checks if it supports the WebP format. If so, the image in WebP format is loaded.
- The plugin does not make redirects in default mode, so the URL is always the same. Only the MIME type of the image changes to `image/webp`.
- No redirects means no cache issues, faster and trouble-free operation of your website. If you want to know more about how it works, check out [the plugin FAQ](#faq) below.
- It does not matter if the image display as an `img` HTML tag or you use `background-image`. It works always!
- In case rewriting by rules from .htaccess file is blocked, a mode is available which loads images via PHP file. Then image URLs are changed, but the logic of operation is the same as in the case of the default mode.
- The final result after image optimization is that your users download less than half of the data, and the website itself loads faster!
- You lose nothing - if you had to remove the plugin, it will remove everything after itself. It does not leave any trace, so you can check it with ease.

#### Convert WebP - it is the future of image optimization!

Optimize images and raise your website to a new level now! Install the plugin and enjoy the website that loads faster by image optimization. Surely you and your users will appreciate it.

#### Support for additional directories

You can convert WebP and optimize images not only from `/uploads` directory but also from `/plugins` and `/themes` directories. This allows full integration with the WebP format!

#### Support to the development of plugin

We spend hours working on the development of this plugin. Technical support also requires a lot of time, but we do it because we want to offer you the best plugin. We enjoy every new plugin installation.

If you would like to appreciate it, you can try [the PRO version](https://url.mattplugins.com/converter-readme-development-support-upgrade). In addition, you will gain access to extra functionalities that will allow you to achieve **even better image optimization results**.

#### Please also read the FAQ below. Thank you for being with us!

== Installation ==

1. Upload the plugin files to `/wp-content/plugins/webp-converter-for-media` directory, or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through `Plugins` screen in WordPress Admin Panel.
3. Use `Settings -> Settings -> Converter for Media` screen to configure the plugin.
4. Click on the button `Start Bulk Optimization` and wait.
5. Check if everything works fine using [this tutorial](https://url.mattplugins.com/converter-readme-installation-instruction).

That's all! Your website is already loading faster!

== Frequently Asked Questions ==

= How to get technical support? (before you ask for help) =

Before you add a new thread, **read all other questions in this FAQ and other threads in [the support forum](https://url.mattplugins.com/converter-plugin-faq-technical-support-forum) first**. Perhaps someone had a similar problem and it has been resolved.

When adding a thread, follow these steps and reply to each of them:

**1.** Do you have any errors on the plugin settings page? Please read [this thread](https://url.mattplugins.com/converter-plugin-faq-technical-support-error-instruction) if you have any errors.

**2.** URL of your website.

**3.** Screenshot of the Help Center tab on the plugin settings screen - please take a screenshot of the ENTIRE page.

**4.** Please do the test, which is described in the FAQ in the question "How to check if the plugin works?". Please send a screenshot of Devtools with the test results.

Please remember to include the answers to all questions by adding a thread. It is much easier and accelerates the solution of your problem.

= Configuration for Nginx =

For Nginx server that does not support .htaccess rules, additional Nginx server configuration is required for the plugin to function properly.

Follow the 4 steps below **(please do all of them)**:

**Step 1**

Find the configuration file in one of the paths *(remember to select configuration file used by your vhost)*:
- `/etc/nginx/sites-available/` or `/etc/nginx/sites-enabled/`
- `/etc/nginx/conf.d/`

and add this code *(add these lines at the beginning of the `server { ... }` block)* - **remember to add these rules before any other `location {}` rules**:

`# BEGIN Converter for Media`
`set $ext_avif ".avif";`
`if ($http_accept !~* "image/avif") {`
`	set $ext_avif "";`
`}`
``
`set $ext_webp ".webp";`
`if ($http_accept !~* "image/webp") {`
`	set $ext_webp "";`
`}`
``
`location ~ /wp-content/(?<path>.+)\.(?<ext>jpe?g|png|gif|webp)$ {`
`	add_header Vary Accept;`
`	expires 365d;`
`	try_files`
`		/wp-content/uploads-webpc/$path.$ext$ext_avif`
`		/wp-content/uploads-webpc/$path.$ext$ext_webp`
`		$uri =404;`
`}`
`# END Converter for Media`

[Here](https://url.mattplugins.com/converter-plugin-faq-nginx-configuration-example) is an example of what a properly added Nginx configuration looks like (this is an example Nginx configuration, but in most cases it looks similar). Note where the rules marked with a red frame are placed.

**Step 2**

Then add support for the required MIME types, if they are not supported. Edit the configuration file:
- `/etc/nginx/mime.types`

and add this code *(add these lines inside the `types { ... }` block)*:

`image/webp webp;`
`image/avif avif;`

**Step 3**

After making changes, remember to restart the machine:

`systemctl restart nginx`

In case of problems, please contact us in [the support forum](https://url.mattplugins.com/converter-plugin-faq-nginx-configuration-contact). We will try to help.

**Step 4**

Also see question "Configuration for Nginx Proxy" in the FAQ below.

= Configuration for Nginx Proxy =

If in the plugin settings page you see the Server configuration error with an error code: **bypassing_apache**, **rewrites_not_executed** or **rewrites_cached**, it means a problem with Nginx Reverse Proxy fof static files or Nginx Caching fof static files.

To solve this problem, look for rules of this type in one of the main Nginx configuration files for the domain (the list of extensions in the location condition may vary, so look for similarities):

`location ~* ^.+\.(css|js|jpg|jpeg|png|gif|webp|ico|eot|otf|woff|woff2|ttf)$ {`
`	expires max;`
`...`

or

`location ~* ^.+\.(css|js|jpe?g|png|gif|webp|ico|eot|otf|woff|woff2|ttf)$ {`
`	expires 1M;`
`	try_files $uri @proxy;`
`...`

If you find such rules, remove the following formats from them:
- `jpg` and `jpeg` or `jpe?g`
- `png`
- `gif`
- `webp`

After making changes, remember to restart the service:

`systemctl restart nginx`

= Error on plugin settings screen? =

If you have an error on the plugin settings screen, first of all, please read it carefully. They are displayed when there is a problem with the configuration of your server or website.

The messages are designed to reduce the number of support requests that are repeated. It saves your and our time. Please read [this thread](https://url.mattplugins.com/converter-plugin-faq-configuration-error-instruction) for more information.

= Error while converting? =

You can get several types of errors when converting. First of all, carefully read their content. For the most part, you can solve this problem yourself. Try to do this or contact the server administrator.

If you get an error: `File "%s" does not exist. Please check file path.` means that the [file_exists()](https://www.php.net/manual/en/function.file-exists.php) function in PHP returned `false` using the file path given in the error message. Check this path and make sure it is correct.

If you get an error: `File "%s" is unreadable. Please check file permissions.` means that the [is_readable()](https://www.php.net/manual/en/function.is-readable.php) function in PHP returned `false` using the file path given in the error message. Check the permissions for the file and the directory in which the file is located.

If you get an error: `"%s" is not a valid image file.` means that the file is damaged in some way. Download the file to disk, save it again using any graphics program and add it again to the page. If the error applies to individual images then you can ignore it - just the original images will load, not WebP.

If you get an error: `Image "%s" converted to .webp is larger than original and converted .webp file has been deleted.` means the original image weighed less than WebP. This happens when images have been compressed before. Disable the *"Automatic removal of files in output formats larger than original"* option in plugin settings to force always using WebP.

= What are requirements of plugin? =

Practically every hosting meets these requirements. You must use PHP at least 7.0 and have the `GD` or `Imagick` extension installed. **The extension must support `WebP format`.** If you have an error saying that the GD or Imagick library is not installed, but you have it installed then they are probably incorrectly configured and do not have WebP support.

They are required native PHP extensions, used among others by WordPress to generate thumbnails. Your server must also have the modules `mod_mime`, `mod_rewrite` and `mod_expires` enabled.

An example of the correct server configuration can be found [here](https://url.mattplugins.com/converter-plugin-faq-plugin-requirements-configuration-image). The link to your current configuration can be found in the Help Center tab on plugin settings screen.

**Note the items marked in red.** If the values marked in red do not appear in your case, it means that your server does not meet the technical requirements. Pay attention to the **WebP Support** value for the GD library and **WEBP in the list of supported extensions** for the Imagick library.

In a situation where your server does not meet the technical requirements, please contact your server Administrator. We are not able to help you. Please do not contact us about this matter, because this is a server configuration problem, not a plugin.

Also, REST API must be enabled and work without additional restrictions. If you have a problem with it, please contact the Developer who created your website. He should easily find the issue with the REST API not working.

= How to check if the plugin works? =

You can find more information on how the plugin works in [our manual](https://url.mattplugins.com/converter-plugin-faq-plugin-check-instruction).

= How to change the path to uploads? =

This is possible using the following types of filters to change default paths. It is a solution for advanced users. If you are not, please skip this question.

Path to the root installation directory of WordPress *(`ABSPATH` by default)*:

`add_filter( 'webpc_site_root', function( $path ) {
	return ABSPATH;
} );`

Paths to directories *(relative to the root directory)*:

`add_filter( 'webpc_dir_name', function( $path, $directory ) {
	switch ( $directory ) {
		case 'uploads':
			return 'wp-content/uploads';
		case 'webp':
			return 'wp-content/uploads-webpc';
		case 'plugins':
			return 'wp-content/plugins';
		case 'themes':
			return 'wp-content/themes';
	}
	return $path;
}, 10, 2 );`

**Note that the `/uploads-webpc` directory must be at the same nesting level as the `/uploads`, `/plugins` and `/themes` directories.**

Prefix in URL of `/wp-content/` directory or equivalent *(used in .htaccess)*:

`add_filter( 'webpc_htaccess_rewrite_path', function( $prefix ) {
	return '/';
} );`

For the following sample custom WordPress structure:

`...
├── web
	...
	├── app
	│	├── mu-plugins
	│	├── plugins
	│	├── themes
	│	└── uploads
	├── wp-config.php
	...`

Use the following filters:

`add_filter( 'webpc_site_root', function( $path ) {
	return 'C:/WAMP/www/project/web'; // your valid path to root
} );
add_filter( 'webpc_htaccess_rewrite_path', function( $prefix ) {
	return '/';
} );
add_filter( 'webpc_dir_name', function( $path, $directory ) {
	switch ( $directory ) {
		case 'uploads':
			return 'app/uploads';
		case 'webp':
			return 'app/uploads-webpc';
		case 'plugins':
			return 'app/plugins';
		case 'themes':
			return 'app/themes';
	}
	return $path;
}, 10, 2 );`

After setting the filters go to `Settings -> Converter for Media` in the admin panel and click the `Save Changes` button. `.htaccess` files with appropriate rules should be created in the directories `/uploads` and `/uploads-webpc`.

= How to exclude paths from converting? =

To exclude selected directories, use the following filter:

`add_filter( 'webpc_supported_source_directory', function( bool $status, string $directory_name, string $server_path ): bool {
    $excluded_directories = [ 'my-directory' ];
    if ( in_array( $directory_name, $excluded_directories ) ) {
        return false;
    }
    return $status;
}, 10, 3 );`

To exclude selected files use the following filter *(in this case with the suffix "-skipwebp" in a filename, e.g. image-skipwebp.png)*:

`add_filter( 'webpc_supported_source_file', function( bool $status, string $file_name, string $server_path ): bool {
    $excluded_suffix = '-skipwebp';
    if ( strpos( $file_name, $excluded_suffix . '.' ) !== false ) {
        return false;
    }
    return $status;
}, 10, 3 );`

Argument `$server_path` is the absolute server path to a directory or file. Inside the filters, you can apply more complicated rules as needed.

Filters run before images are converted - they no longer support converted images. You have to delete them manually if they should not be converted.

= Support for custom directories =

The plugin supports the following directories by default:
- `/gallery`
- `/plugins`
- `/themes`
- `/uploads`

If you want to add support for a custom directory, add the following code to the functions.php file in your theme directory *(use a correct directory name instead of `custom-directory`)*:

`add_filter( 'webpc_source_directories', function ( $directories ) {
	$directories[] = 'custom-directory';
	return $directories;
} );`

Remember that this directory must be located in the `/wp-content` directory.

= How to run manually conversion? =

By default, all images are converted when you click on the `Start Bulk Optimization	` button. In addition, conversion is automatic when you add new files to your Media Library.

Remember that our plugin takes into account images generated by WordPress. There are many plugins that generate, for example, images of a different size or in a different version.

If you would like to integrate with your plugin, which generates images by yourself, you can do it. Our plugin provides the possibility of this type of integration. This works for all images in the `/wp-content` directory.

It is a solution for advanced users. If you would like to integrate with another plugin, it's best to contact the author of that plugin and give him information about the actions available in our plugin. This will help you find a solution faster.

You can manually run converting selected files, you can use the action to which you will pass an array with a list of paths *(they must be absolute server paths)*:

`do_action( 'webpc_convert_paths', $paths, true );`

An alternative method is to manually start converting the selected attachment by passing the post ID from the Media Library. Remember to run this action after registering all image sizes *(i.e. after running the `add_image_size` function)*:

`do_action( 'webpc_convert_attachment', $post_id, true );`

To delete manually converted files, use the following action, providing as an argument an array of absolute server paths to the files *(this will delete manually converted files)*:

`do_action( 'webpc_delete_paths', $paths );`

= Support for WP-CLI =

The plugin supports WP-CLI, which enables faster image conversion from the server level. More information on how to get started with WP-CLI can be found in [the Handbook](https://make.wordpress.org/cli/handbook/guides/quick-start/). The supported commands are described below.

Checking how many maximum images for conversion are on website:

`wp converter-for-media calculate`

Converting all images:

`wp converter-for-media regenerate`

Converting all images (with "Force convert all images again" option):

`wp converter-for-media regenerate --force`

= Does plugin support CDN? =

The website files (WordPress files) and the images from the Media Library must be on the same server. If they are, everything should work fine.

If only your images are on another CDN server, unfortunately correct operation is impossible, because such images are managed by another server.

== Screenshots ==

1. General tab of the plugin settings
2. Advanced tab of the plugin settings
3. Bulk optimization of images
4. Optimization statistics of Media Library

== Changelog ==

= 5.9.3 (2023-07-04) =
* `[Fixed]` Corrupted filenames in image URLs using Bypassing Nginx loading mode

= 5.9.2 (2023-07-03) =
* `[Fixed]` Suffix "-optimized" in image URLs using Bypassing Nginx loading mode
* `[Fixed]` Right-to-left styling of plugin settings page
* `[Added]` Error message when using WP-CLI when Conversion method is not available

= 5.9.1 (2023-05-24) =
* `[Changed]` Error message for rewrites_not_executed error in server configuration

= 5.9.0 (2023-05-20) =
* `[Fixed]` Conversion of images in WP-CLI using force flag
* `[Changed]` Error messages on plugin settings page
* `[Added]` Skipping backup files generated by other image optimization plugins

= 5.8.6 (2023-04-29) =
* `[Fixed]` Generating XML files using Pass Thru loading mode

= 5.8.5 (2023-04-07) =
* `[Added]` Skipping .jpg.webp, .jpeg.webp, .png.webp, and .gif.webp files generated by other image optimization plugins
* `[Added]` New parameter (to force reconversion) for webpc_convert_paths hook
* `[Added]` New parameter (to force reconversion) for webpc_convert_attachment hook

= 5.8.4 (2023-03-20) =
* `[Fixed]` Generating rules in .htaccess file when real DOCUMENT_ROOT path is different from WordPress root directory

= 5.8.3 (2023-03-09) =
* `[Fixed]` Converting images without EXIF data support using GD method
* `[Added]` Exception for blocked REST API endpoints by JWT Auth plugin

= 5.8.2 (2023-03-02) =
* `[Changed]` Written content in plugin settings
* `[Added]` Support for WordPress 6.2

= 5.8.1 (2023-02-27) =
* `[Fixed]` Converting using GD method without `exif_read_data` function available
* `[Fixed]` Redirects of images using Bypassing Nginx loading mode

= 5.8.0 (2023-02-20) =
* `[Fixed]` Generating output paths in WordPress Multisite Network
* `[Fixed]` Replacing URLs in Pass Thru loading mode for themes without get_header hook
* `[Changed]` Automatic clearing of cache generated by LiteSpeed Cache plugin
* `[Changed]` Error message for bypassing_apache error in server configuration
* `[Added]` Image loading mode: `Bypassing Nginx` (use when you have a problem with the bypassing_apache error)
* `[Added]` Support for defined /uploads directory using UPLOADS constant
* `[Added]` Support for Orientation parameter in EXIF data
* `[Added]` Automatic clearing of cache generated by Breeze plugin
* `[Added]` Automatic clearing of cache generated by Cache Enabler plugin
* `[Added]` Automatic clearing of cache generated by Hummingbird plugin
* `[Added]` Automatic clearing of cache generated by SiteGround Optimizer plugin
* `[Added]` Automatic clearing of cache generated by W3 Total Cache plugin
* `[Added]` Automatic clearing of cache generated by WP Fastest Cache plugin
* `[Added]` Automatic clearing of cache generated by WP-Optimize plugin
* `[Added]` Automatic clearing of cache generated by WP Super Cache plugin
* `[Added]` Support for defined value of WP_HOME for testing rewrites

See [changelog.txt](https://url.mattplugins.com/converter-readme-changelog) for previous versions.

== Upgrade Notice ==

None.
