PHPackages mhe/imagetools - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Image & Media](/categories/media) 4. / 5. mhe/imagetools ActiveLibrary[Image & Media](/categories/media) mhe/imagetools ============== Tools for generating responsive images v1.0.3(1y ago)01421BSD-3-ClausePHPPHP ^8.0 Since Jul 19Pushed 1y ago1 watchersCompare [ Source](https://github.com/martinheise/imagetools)[ Packagist](https://packagist.org/packages/mhe/imagetools)[ RSS](/packages/mhe-imagetools/feed)WikiDiscussions main Synced 3w ago READMEChangelog (4)Dependencies (1)Versions (7)Used By (1) Image tools =========== [](#image-tools) This module contains logic to calculate multiple scaled image sizes from one source image and configuration options. It is meant to create appropriate `srcset`and `sizes` attributes for responsive images that best fit the given image and information about the HTML/CSS context. It only contains business logic to define the expected sizes. The actual handling of the image data, like resizing, caching of the result etc. is not handled by the module, but done by the calling code, the interface `ImageData` serves as main connection point. Background ---------- [](#background) “Humans shouldn’t be doing this” – some inspiring thoughts on deciding which image resolutions to use in responsive output can be found in this article by Jason Grigsby: [Image Breakpoints](https://cloudfour.com/thinks/responsive-images-101-part-9-image-breakpoints/), especially [Setting image breakpoints based on a performance budget](https://cloudfour.com/thinks/responsive-images-101-part-9-image-breakpoints/#setting-image-breakpoints-based-on-a-performance-budget) Installation ------------ [](#installation) Install with composer: ``` composer require mhe/imagetools ^1.0 ``` Usage overview -------------- [](#usage-overview) - Implement interface `Mhe\Imagetools\Data\ImageData` as a wrapper for your images and processing methods - create a `Mhe\Imagetools\Data\RenderConfig` object holding options and context information about the specific image layout context: ``` $config = new RenderConfig("(max-width: 1000px) 100vw, 1000px"); ``` - create a new `Mhe\Imagetools\ImageResizer` and let it process the source image with given configuration: ``` $resizer = new ImageResizer(); $result = $resizer->getVariants($srcimg, $config); ``` - The result is an array of images you can use to output a `srcset` attribute For a small demonstration of the very basic usage see [mhe/imagetools-cli](https://github.com/martinheise/imagetools-cli). A more advanced usage is [mhe/silverstripe-responsiveimages](https://github.com/martinheise/silverstripe-responsiveimages), a module for CMS Silverstripe. Configuration and options ------------------------- [](#configuration-and-options) ### ImageResizer options [](#imageresizer-options) When creating a new `ImageResizer` you can provide these parameters to tweak the general behaviour: - `min_viewport_width`: minimum viewport width to consider (default: 320) - `max_viewport_width`: maximum viewport width to consider, e.g. for fullwidth images (default: 2400) - `rem_size`: used to translate values in rem unit to px (default: 16) ### RenderConfig options [](#renderconfig-options) A `RenderConfig` contains several options used for the calculations for a specific image – usually they are the same for multiple images used in the same layout context and/or CSS class, so you would have one configuration for Hero images, one for slider images, one for teaser images etc. #### sizes [](#sizes) The main parameter of `RenderConfig`. It matches the `sizes` attribute of a desired `ìmg` element, telling the ImageResizer in which actual layout sizes (widths) the image will output on different screensizes. This information can be deducted from the page layout usually defined in CSS, depending on the complexity of your layout it can get a bit more complicated to count in all conditions, often you just have to add up a couple of container margins etc. In doubt: if the information don’t exactly match the image sizes it probably doesn’t effect the result very much – a rough approximation is better than no information. *Some examples:* Full width image with margins of 16px on each side: `calc(100vw - 32px)` Image has full width with margins in mobile view, displayed in a 2-column grid on desktop: `(max-width: 720px) calc(100vw - 32px), calc(50vw - 40px)` Image has full width with margins in mobile view, displayed in a 2-column grid on desktop, and is limited to a fixed width on large screens: `(max-width: 720px) calc(100vw - 32px), (max-width: 1680px) calc(50vw - 40px), 800px` #### sizediff [](#sizediff) This is the desired filesize difference in bytes between two different renditions. It will not be reached exactly, but rather a rough target. Lower values mean more generated files, better matching the particular user conditions, but of course more load on generating images. #### maxsteps [](#maxsteps) Set a limit on the number of renditions generated, has precedence of `sizediff`. With low `sizediff` values and large images this will assure that you don’t end up with vast amount of images generated. #### highres [](#highres) Set to either `2` or `3` adds up extra levels for high resolution screens. If e.g. the maximum calculated image width is 1200px, also renditions for 2400px (or even 3600px) are created. #### rendersizes [](#rendersizes) Request specific image widths to generate for specific purposes. If given the other parameters are ignored. Can be helpful in specific cases – if you *only* use this kind of configuration you probably don’t need this module at all ... ### Health Score 30 — LowBetter than 62% of packages Maintenance42 Moderate activity, may be stable Popularity11 Limited adoption so far Community9 Small or concentrated contributor base Maturity49 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~73 days Total 4 Last Release 484d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/bdc925a420ee741e57764c199a926d0edb8dbcfe1f4528b2f0519c465461720e?d=identicon)[martinheise](/maintainers/martinheise) --- Top Contributors [![martinheise](https://avatars.githubusercontent.com/u/16256376?v=4)](https://github.com/martinheise "martinheise (9 commits)") ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/mhe-imagetools/health.svg) ``` [![Health](https://phpackages.com/badges/mhe-imagetools/health.svg)](https://phpackages.com/packages/mhe-imagetools) ``` ### Alternatives [char0n/ffmpeg-php PHP wrapper for FFmpeg application 495236.3k1](/packages/char0n-ffmpeg-php)[goat1000/svggraph Generates SVG graphs 133890.0k3](/packages/goat1000-svggraph)[imagekit/imagekit PHP library for Imagekit 46877.3k10](/packages/imagekit-imagekit)[gravatarphp/gravatar Gravatar URL builder which is most commonly called as a Gravatar library 12644.1k2](/packages/gravatarphp-gravatar) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)