TinyImg 2.2.1 pl 2

License Agreement
Supported Versions
WoltLab Suite 3.0
WoltLab Suite 3.1

Scales and compresses uploaded image files.

Too many attached, big images can cause a lot of trouble in active communities. Hardly any user bothers to scale images before uploading to a "reasonable" size, let alone to compress the image files before uploading. Finally resulting in huge backups of gigabytes and (especially for mobile devices) unnecessarily high load times (for example, when calling topics in forum).

In the past, we've got the problem under control by some pretty good approaches. First and foremost the (no longer available) extension "Attachment Scaling" by DevLabor and not to forget our (also no longer available) TinyImg extension of the first generation.

Now, we've combined all the benefits of both extensions in one package and added a variety of new features to give you, as a community operator, maximum flexibility in scaling, converting, and compressing attachments of images. The result is our second-generation TinyImg extension.

Propotional scaling of image files to defined maximum dimensions
Client-side scaling (scaling directly in the user's browser)
Server-side scaling
File renaming
Text watermark
Image watermark
Recovery & Postprocessing from the Attachment Overview in ACP

Frequently asked questions

Q: What are the potential savings when using scaling and compression?

A: This can not be answered in general because the performance depends on a large number of factors. However, with scaling and compression enabled, it's possible to save over 90% of the original file size, because cell phone cameras are getting better and better and producing higher-resolution images. In one of the largest communities we maintain, with an average of 1,100 posts per day and over 100 image attachments a day, using TinyImg saved over 80% of the data volume generated by image files. In our support forum, however, 1,568 uploaded image files with a total size of 209.23 megabytes saved exactly 64.94% (135.87 megabytes).

Q: What are the advantages of client-side scaling over server-side scaling?

A: By far the biggest advantage of client-side scaling is saving traffic (or the seemingly finite resource "data volume"). If images are first processed by the server, the original image in its original file size must first be fully uploaded. Due to the client-side processing, the images are scaled before the upload, which not only relieves the load on the server, but above all significantly less traffic. Also, with client-side scaling, there is no need to increase the maximum allowed file size to allow uploading large image files. Last but not least, the client-side scaling also relieves the load on the server, as it no longer has to take care of shrinking the images accordingly.

Q: Does client-side scaling work anytime, anywhere?

A: Basically, client-side scaling should work in all modern browsers

Q: Are images rescaled by the server after client-side scaling?

A: If the scaling option is enabled, an image is always processed by the server during the upload process, regardless of whether client-side scaling is enabled or not. The main reason for this is that the server does not know if client-side scaling works as intended, or is not supported by the browser for some unknown reason. However, if the server receives an image in the "correct" dimensions, it will not rescaled by the server.

Q: Are images scaled up that are too small?

A: No.

Q: For watermarks of type "text", can I insert the username of the user who uploaded the image?

A: Yes, this is easily possible by using {$username}. Other wildcards are currently not supported.

Q: What happens by activating the backup function?

A: The backup function saves the original images in a separate directory before being processed by the server. In addition, all meta informations of the original image (e.g. file name, file size and image dimensions) are stored in the database. The former allows the restoration of images, the latter is mainly used for various statistics. Disabling the backup function has the disadvantage, that the original images are no longer available after being processed by TinyImg, but the advantage that no additional space is occupied on the server.

Q: How does the restore work?

A: There are two possibilities for the restore: Individual image files can be restored in the administration area via the file attachment overview, mass processing is possible via the function "Update displays" in the administration area.

Q: Where does TinyImg find everywhere?

A: Currently, TinyImg only includes the internal file attachment feature. Expanding to other areas (such as the gallery or the media administration) is already in planning stage or even in progress.

Q: Can I test the product somewhere?

A: TinyImg can be tested directly in our support forum at support.softcreatr.com, as well as with our demo installation at demo.softcreatr.com.

  • Version 2.2.1 pl 2

    - Bugfix

    - Fixed WSC 3.0 compatibility issue

  • Version 2.2.0

    - Optimized options for scaling animated GIF files

    - Improved detection of animated GIF files

    - Enabled option "Create backup" by default (fresh installations only)

  • Version 2.1.1 pl 1


    You can get the update package for version 2.1.0 PL 1 at https://www.softcreatr.com/sc-…ckageID=2981&fileID=11127

  • Version 2.1.0 pl 1

    Initial Plugin Store Release

Customers Who Bought This File Also Bought