FileOptimizer 5.70.247

FileOptimizer is a lossless file size optimizer supporting AIR, APK, APNG APPX, BMP, CBZ, CHM, DOCX, DIB, DLL, EPUB, EXE, FAX, GIF, GZ, ICO, JAR, JPEG, LIB, MNG, MP3, MPP, OBJ, PNG, PPTX, ODT, OGG, OGV, PDF, PUB, SCR, SWF, TIF, VSD, WEBP, XAP, XLSX, and ZIP file formats among others.

It keeps the behavior of the file untouched, but with its size reduced thanks to several re-compression and optimization techniques.

Key features:

  • Suitable for home users that need to speedup file transfers no matter if they are in email attachments, P2P or shared upload servers.
  • Suitable for webmasters to increase the page load speed.
  • Suitable for web developers to reduce content weight.
  • Suitable for desktop developers in any platform (Windows, Linux, MacOS, ...) to reduce distribution sizes and reduce load times.
  • Suitable for mobile developers (Android, iOS, Windows Phone, ...) to reduce distribution sizes and reduce load times.
  • Suitable for server administrators that could integrate FileOptimizer via command line.
  • Suitable for content creators and distributors to reduce content weights.

What's new in this version:

  • Improved PNG compression ratio and speed updating to PngOptimizer 2.3.
  • Upgraded Gifsicle to 1.71 (custom build).
  • Added support for Gifsicle x64 too (custom build).
  • Upgraded jpegoptim to 1.3.1 beta (custom build with libjpeg 9).
  • Prevented zRecompress generating larger files.
  • Closing windows is now more responsive.
  • Some minor optimizations and code cleanup.

Download: FileOptimizer 5.70.247 | 17.5 MB (Open Source)
View: FileOptimizer Website

Report a problem with article
Previous Story

Did Nokia's board hold an unscheduled meeting this week?

Next Story

Windows Phone 8.1 notifications center + UI changes allegedly revealed in video [Update]

8 Comments

Commenting is disabled on this article.

I'm thinking of security implications, not those of this application but those of compressed files.

I'll try to state things in understandable English :

If a given file, .exe in particular, has been checked by, say, VirusTotal as potentially harmful, and if I compress that file with this application, then return it to VirusTotal, it may simply pass the tests successfully, given that AV engines work with lists and not with file behavior.

Is this correct?

It may or may not. Compressed counterpart will have a modified entry point which itself registers as a potential threat in many engines, because two reasons:

* changing entry point is the easiest way to attach harmful code
* malware authors usually use some kind of compression for obfuscation

Even more, if a certain AV doesn't pick up any such exe files, I'd cast a heavy doubt on its abilities to detect threats in general. Modern AV engines do have limited behavior detection to combat self-modifying malware.

Now that is mostly interesting. Thanks for this valuable information, +Phouchg.
This does mean that the process leading to AV signatures is far more elaborated than I imagined.

It seems this has a very limited application. Trading rather miniscule gains of space for a large increase in required CPU time? Reminds of le old DriveSpace that "optimized" floppies, but rarely anybody could read them afterwards, floppies failing as they did, and it was painfully slow.