- How do I install jorisnoo/statamic-imageboss in a Statamic project?
- Install the addon with Composer using composer require jorisnoo/statamic-imageboss, then publish its configuration so the ImageBoss settings are available to your app. Add your ImageBoss token as an environment variable and reference it from the config file so credentials stay out of version control. After changing config or environment values, clear your config cache so the signed URL generation picks up the new token.
- What Laravel, PHP and Statamic versions does statamic-imageboss require?
- Version 0.4.0 of this addon targets Laravel 12 or newer, PHP 8.3 or newer, and Statamic 5 through 6. It explicitly drops support for Laravel 11 and PHP 8.2, so older stacks will fail the Composer platform check. If you are not yet on those minimums, either upgrade your platform first or pin a pre-0.4.0 release until you do.
- How do I generate responsive ImageBoss image URLs in Antlers templates?
- The addon exposes image transformation through Statamic assets so you can output ImageBoss URLs directly from your Antlers templates. You pass the transformation parameters such as width, height, fit and format, and the addon builds a properly signed ImageBoss URL for you. That means you can ship responsive srcset markup without maintaining your own resizing pipeline or signing logic.
- What is the Glide fallback in this Statamic ImageBoss addon?
- Glide is Statamic's built-in image manipulation pipeline, and the addon falls back to it when ImageBoss is unavailable or not configured. This keeps image rendering working locally, in CI, or during an ImageBoss outage instead of producing broken image URLs. It also makes the addon safer to adopt gradually, since you can enable ImageBoss in production while keeping local development on Glide.
- What broke in statamic-imageboss 0.4.0 and how do I migrate?
- The 0.4.0 release drops Laravel 11 and PHP 8.2 support and renames the ImageBoss signing secret configuration value to token. Migration means upgrading your Laravel, PHP and Statamic versions first, then updating the package, renaming the secret key to token in config and environment files, and clearing config caches. After that, verify that signed ImageBoss URLs still resolve correctly before deploying to production.
- Where should I store the ImageBoss token for each environment?
- Keep the token in an environment variable and reference it from the addon's config file rather than committing it to the repository. Each environment, including staging and production, should have its own ImageBoss token so rotation and revocation stay isolated. Document a token rotation runbook, because a missing or stale token will break signed URL generation immediately after a config change.
- Does the addon purge the ImageBoss cache when I reupload an asset?
- Yes, version 0.4.0 adds automatic cache purging when an asset is reuploaded, so ImageBoss does not keep serving the old transformed image. This introduces an external ImageBoss API dependency in the reupload flow, so failures can surface as stale images or interrupted uploads depending on whether purging is synchronous or queued. Test reuploads in staging and confirm whether your ImageBoss plan requires extra API permissions or has rate limits.
- Why are my ImageBoss signed image URLs failing or returning errors?
- The most common cause is a missing, incorrect or rotated token, since signed URLs cannot be validated without the correct secret. Check that the token is set in the right environment, that config caches were cleared after the secret to token rename, and that the ImageBoss account is active. If ImageBoss itself is unreachable, image delivery can be affected across the site, so confirm service status before debugging your own configuration.
- How do I test an ImageBoss migration before deploying to production?
- Run a staging pass that covers URL signing, animated image support, focal-point defaults and asset reupload cache purging. The addon ships an expanded Pest test suite, which helps validate the package itself, but you should still regression-test existing layouts because default center focal points can subtly change how images are cropped. Keep a rollback path to the previous package version in case signed URLs or purge behavior fail after deployment.
- Is jorisnoo/statamic-imageboss actively maintained and what are the alternatives?
- The package has active releases and improved test coverage with the Pest v4 upgrade, but 0.4.0 narrows runtime compatibility, so you need to track Laravel, PHP and Statamic upgrade cycles more closely. The main alternative is Statamic's native Glide pipeline, which avoids an external image service but leaves resizing and optimization on your own infrastructure. Teams that want offloaded image transformation and already run a current Statamic stack will get the most value from this addon.