ceven

TinyPNG

Shrinks image file sizes across your storage buckets and CMS without losing quality, converts formats for web performance, and monitors your monthly compression quota.

Try TinyPNG in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native TinyPNG integration

    • Describe the outcome and Ceven picks the right TinyPNG calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your TinyPNG data, across all 5 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke TinyPNG access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in TinyPNG, when, and on whose behalf.
    • The agent pauses and asks when TinyPNG is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach TinyPNG.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every TinyPNG action to support review and sign off.

Supported tools

Every action Ceven's agents can run on TinyPNG, and when to use it.

Get compression count
Use this when you need to monitor your TinyPNG API usage and check how many compressions remain in your monthly plan.
Shrink and get image ID
Use this when you only need the compressed image identifier from the API response location header without downloading the file immediately.
Compress and convert image
Use this when you need to optimize an image and change its format to AVIF, WebP, JPEG, or PNG for better web performance.
Compress and preserve metadata
Use this when critical metadata like copyright, creation date, or GPS location must be retained in the output file.
Compress and store in Azure
Use this when you want to optimize images and upload them directly to Azure blob storage in one single step.
Download compressed image
Use this after compressing an image to retrieve the final optimized file using its unique image ID.
Get TinyPNG Compression Count
Tool to retrieve the number of compressions made this month. use when you need to monitor your tinypng api usage.
Compress and Store Image in Azure
Tool to compress an image using tinify and upload it directly to azure blob storage. use when you want to optimize images and store them to azure in one step.

8 actions · scroll to see them all

Frequently asked questions

Ceven monitors your TinyPNG compression count in real time to prevent workflow failures. When a workflow triggers a batch of images, the agent first checks your remaining monthly allowance. If you are nearing your limit, the agent can send an alert to your Slack or email so you can upgrade your plan before the API starts returning errors. You can also set a hard cap within the Ceven workflow settings to stop all compression once a certain threshold is hit. This prevents unexpected overage charges on your TinyPNG account and ensures that critical system processes do not crash due to a 429 rate limit error during a large asset migration.
Yes. While standard lossy compression often strips metadata to save more space, Ceven uses the specific preserve metadata action from TinyPNG. When you configure your workflow, you can explicitly tell the agent which fields to keep, such as GPS location or copyright tags. The agent sends these requirements to the TinyPNG API, which then processes the image while leaving those specific metadata chunks untouched. This is essential for photography portfolios or real estate sites where location data is a requirement for the end user but file size still needs to be minimized for fast loading on mobile devices.
Ceven leverages the full range of TinyPNG capabilities, meaning it can process and optimize PNG, JPEG, and WebP files. Beyond simple compression, the agent can handle format conversion. For example, you can set up a workflow that takes a high resolution PNG and converts it into a WebP or AVIF file. This is highly recommended for modern web development because these formats provide superior compression without a noticeable loss in visual quality. The agent handles the conversion logic and ensures the resulting file is delivered to your storage provider or CMS in the correct format for your frontend implementation.
Ceven uses a direct pipeline between TinyPNG and Azure blob storage. Instead of downloading the compressed image to a local server and then uploading it again, the agent instructs TinyPNG to push the optimized result directly to your Azure container. You provide the Azure credentials and the target container name within the Ceven connection settings. Once the compression is complete, TinyPNG transfers the file, and Ceven receives a confirmation of the successful upload. This reduces the latency of your image pipeline and eliminates the need for temporary disk space, making it an ideal setup for high volume e commerce sites.
Yes, TinyPNG has a strict file size limit of 5MB per image for API requests. If your workflow attempts to send a file larger than 5MB, the TinyPNG API will return an error and the compression will fail. To handle this, Ceven can be configured with a pre check step that inspects the file size before calling the API. If the file exceeds the 5MB limit, the agent can either skip the image, send a notification to a human for manual resizing, or route it to a different processing tool. This ensures your workflow remains stable even when users upload oversized raw assets.
TinyPNG uses smart lossy compression. This means it selectively removes data that the human eye cannot perceive to achieve significant reductions in file size. While this is not a lossless process, the algorithm is designed to maintain high visual fidelity. In a Ceven workflow, this means your images will look nearly identical to the originals but will load much faster. If your specific use case requires absolute lossless compression for medical imaging or high end archival work, this tool may not be the right fit, as the primary goal of TinyPNG is web optimization and speed rather than perfect bit for bit reproduction.
Ceven stores your TinyPNG API key using AES 256 encryption at rest. The key is never exposed to the model or the end user in plain text. When an agent needs to perform a compression task, the key is retrieved from our secure vault and injected into the request header for that specific API call. We follow the principle of least privilege, ensuring that only the necessary components of the workflow engine have access to the credential. You can rotate your API key in the TinyPNG dashboard at any time and update it within the Ceven connection settings to maintain a high security posture for your account.
Absolutely. You can build a Ceven workflow that iterates through a list of image URLs or a folder in a cloud storage bucket. The agent will loop through each item, call the TinyPNG compress and convert action, and save the result back to your destination. To avoid hitting API rate limits during a massive migration, you can configure the agent to process the images in batches with a small delay between each group. This allows you to convert thousands of legacy PNGs to WebP in the background without manual intervention, effectively updating your entire site asset library while you focus on other tasks.

Alternatives to TinyPNG

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

ImageOptim logoImageOptimSquoosh logoSquoosh

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect TinyPNG and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free