WeCompress isn’t just a free online compression tool, it’s a way for us to continuously make improvements to our compression engine so that we can be even more effective in reducing the size of your PowerPoint files. With the help of the many customers who agree to share their files that haven’t reduced well, we’re able to analyse and tweak the technology behind WeCompress and all of our Neuxpower products. Even though we’ve only been live for a few months we’ve already been able to make improvements.
We’ve just pushed a few of those improvements live on the site and we thought you’d want to hear about them so here we go:
PowerPoint 2013 XML files
The first improvement we’ve made is a essentially a bug fix. Having received a multitude of different file types through WeCompress we came across an issue where we were unable to compress PowerPoint files created using Office 2013. After doing some digging we found that the issue was only applicable to XML files (PPTX). When we dug a little further we discovered that this all stemmed from an incorrect assumption in the code we were using to optimize files. It turns out that Office 2013 could produce files that were of a slightly different composition to other versions of Office.
I’m happy to confirm that this has been resolved and we can reduce the size of these files as well as their Office 2013 counterparts (DOCX & XLSX). So far we know this fixes at least two problems reported by our customers but considering there’s still lots of individuals using Office 2013 we’re confident that it will be applied to many more files in the future.
Image Filled Shapes
Improvement number two relates to images found within a PowerPoint file. Previously our compression engine had been unable to reduce the size of images which had been set as a background fill for a shape inserted into a slide show (see image below).
This is a common feature of Adobe products when exporting from PDF to PPT, they export images as shapes with a background and thus our software did not recognise the image files when reviewing their contents. We came across a fair few examples without initially being able to see why the files weren’t being reduced, but once we clocked the reason this was occuring we were able to resolve it. So now your image fills will also be compressed like a normal image. Again, this is a resolution that we’re positive will be applicable to many more files
This is another example of how WeCompress is not only delivering the best compression levels possible for your files, but giving us valuable information so that we can continue to improve our offering to you. It’s a lovely little symbiotic relationship benefiting both parties in equal measure. I’m sure you’ll start to see a lot more improvement posts like this as we really start to harness the data we’re receiving, so watch this space - there’s plenty more where these came from.