Sort source and compressed image folders
Connect
SPIRITT
TinyPNGTinyPNG
Lighter images, ready to ship
SPIRITT turns source images into compressed, resized delivery assets with TinyPNG. Delegate the whole workflow, from collecting files to storing finished variants and tracking monthly compression usage.
What you can do with TinyPNG.
Delivery-ready assets
Compress WebP, JPEG, and PNG files, then resize or convert the compressed images into the variants your site or campaign needs.
Repeatable production
Turn incoming images into organized output packs with source mappings, compression IDs, and a clear record of completed or failed jobs.
Usage you can manage
Check TinyPNG's monthly compression count alongside your work queue to prioritize essential assets and avoid unnecessary repeat processing.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your website assets, creative production, or image delivery operations.
02
Connect TinyPNG
Connect TinyPNG with your API key, and provide access to the source images and destination storage your mission needs.
03
Delegate an outcome
Give SPIRITT your image specifications and delivery destination. It builds and runs the workflow that prepares the finished assets.
Hand over a mission.
Choose a mission. Make it yours.
Put TinyPNG to work.
Put image preparation on autopilot
Questions
TinyPNG, with SPIRITT.
01What can SPIRITT do with TinyPNG images?+
SPIRITT can compress WebP, JPEG, and PNG images, retain the returned image IDs, and download the compressed results. It can also transform compressed images by resizing, converting format, or applying supported metadata preservation settings, and use direct compression-to-Azure storage.
02What access does an image workflow need?+
TinyPNG connects with an API key. SPIRITT also needs access to the source images and wherever the outputs should go. A direct Azure delivery workflow needs the appropriate storage access and destination details; a TinyPNG connection alone does not grant access to your storage.
03Can SPIRITT keep processing new images automatically?+
Yes. SPIRITT can run a scheduled workflow around a connected source folder or job queue. Its job ledger tracks source versions, returned image IDs, completed downloads, and failures so new work is processed separately from finished batches.
04How can this work with our existing asset tools?+
A workflow can collect source images from Google Drive, use TinyPNG for compression and transformations, record results in Google Sheets, and notify the team through Slack. TinyPNG also provides an action that compresses an image and stores the optimized result directly in Azure Blob Storage.
05Can SPIRITT build a custom image preparation tool?+
Yes. It can build an upload portal, preset-based variant generator, or product asset library around TinyPNG. The custom system manages intake, job status, source mappings, and delivery links while TinyPNG performs the supported image operations.
06Does compression guarantee unchanged quality or a faster website?+
No. TinyPNG uses smart lossy compression, so smaller files do not mean pixel-identical output. SPIRITT can measure output sizes and build visual comparisons before files are used. Website speed also depends on delivery, layout, and other resources; monthly compression counts measure usage, not page performance.