XnConvert
Is it not possible to convert animations in GIF or WEBP while maintaining the animation into WEBP?
GIF and WEBP animations
Moderator: xnview
-
xnview
- Author of XnView
- Posts: 47708
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
-
Chrischen
- Posts: 1
- Joined: Wed Apr 22, 2026 10:57 am
Re: GIF and WEBP animations
Hi, first off, thanks for XnCovert. It is a great tool.
I wanted to ask if you plan to add animated WebPs in the future (or already have it on the roadmap) - since the post is already 2 years old - or if this feature is permanently not planned?
Since animated WebP's (img2webp) are supported/part of the official tool chain from google to create WebP's, i am hoping you can just support it too but if not, I understand.
However, should you still not plan to include it (or even as an intermediary), I have another feature requests:
1. Can you please add a (popup) warning that appears each time when the input file list includes animated files (discovered while adding or during the conversion) that those files will not be converted "as expected". This is true for animated gifs or animated webPs but maybe also relevant for other file formats you know are not supported and acts as a safety net for the user.
2. Can you please add an option that moves "unsupported" files "As is" to the defined output folder instead of converting them anyway and therefore losing the important information?
E.g. if a animated GIF (file1.gif) besides other files is in the input folder and i start a conversion to WebP, "file1.gif" will be moved as is, instead of being converted to a unanimated file1.webp regardless. For me personally the move is
UseCase: I plan to convert my collection of images from a variety of formats to webP. However, as I did so, I (luckily) discovered by chance that some folders contained animated GIFs that got turned to unanimated WebP's. Since there is no user feedback about that behavior, I could have just as easily missed that fact and deleted the originals for good (which might have happened to other users already). Thats why i think feature 1 is almost a must have.
However, that does not quite solve the problem but only mitigates it somewhat. Hence my suggestion for feature 2. I suspect, that most users do care more about keeping the animation than the conversion. However, that means (if they know about the original behavior at all), they have to explictly remove gives from the file list and after conversion manually copy the orignal GIF's etc. to the new folder, which could be quite time consuming manual work, if the files are spread out in multiple individual sub-folders. It would be way more convenient, if the programm allows to copy those "unsupported" files to the new structure. This also does not have to be limited to just animated images but also include other "unsupported" files like zip archives, pdfs, documents etc, that are in the same structure.
I wanted to ask if you plan to add animated WebPs in the future (or already have it on the roadmap) - since the post is already 2 years old - or if this feature is permanently not planned?
Since animated WebP's (img2webp) are supported/part of the official tool chain from google to create WebP's, i am hoping you can just support it too but if not, I understand.
However, should you still not plan to include it (or even as an intermediary), I have another feature requests:
1. Can you please add a (popup) warning that appears each time when the input file list includes animated files (discovered while adding or during the conversion) that those files will not be converted "as expected". This is true for animated gifs or animated webPs but maybe also relevant for other file formats you know are not supported and acts as a safety net for the user.
2. Can you please add an option that moves "unsupported" files "As is" to the defined output folder instead of converting them anyway and therefore losing the important information?
E.g. if a animated GIF (file1.gif) besides other files is in the input folder and i start a conversion to WebP, "file1.gif" will be moved as is, instead of being converted to a unanimated file1.webp regardless. For me personally the move is
UseCase: I plan to convert my collection of images from a variety of formats to webP. However, as I did so, I (luckily) discovered by chance that some folders contained animated GIFs that got turned to unanimated WebP's. Since there is no user feedback about that behavior, I could have just as easily missed that fact and deleted the originals for good (which might have happened to other users already). Thats why i think feature 1 is almost a must have.
However, that does not quite solve the problem but only mitigates it somewhat. Hence my suggestion for feature 2. I suspect, that most users do care more about keeping the animation than the conversion. However, that means (if they know about the original behavior at all), they have to explictly remove gives from the file list and after conversion manually copy the orignal GIF's etc. to the new folder, which could be quite time consuming manual work, if the files are spread out in multiple individual sub-folders. It would be way more convenient, if the programm allows to copy those "unsupported" files to the new structure. This also does not have to be limited to just animated images but also include other "unsupported" files like zip archives, pdfs, documents etc, that are in the same structure.