API Reference

The Tinify API allows you to compress and optimize AVIF, WebP, JPEG and PNG images. It is designed as a REST service. The client libraries in various languages make it very easy to interact with the Tinify API.

Installation

Using Composer

You can use the PHP client by installing the Composer package and adding it to your application’s dependencies:

composer require tinify/tinify

Make sure to require Composer’s autoloader:

require_once("vendor/autoload.php");

Using manual installation

If you do not like to use Composer you can also manually install the PHP client. Download the Tinify archive from Github, extract the files to a folder of your choice and include them in your project as shown below.

require_once("lib/Tinify/Exception.php");
require_once("lib/Tinify/ResultMeta.php");
require_once("lib/Tinify/Result.php");
require_once("lib/Tinify/Source.php");
require_once("lib/Tinify/Client.php");
require_once("lib/Tinify.php");

The source code is available on Github.

Authentication

To use the API you must provide your API key. You can get an API key by registering with your name and email address. Always keep your API key secret!

\Tinify\setKey("YOUR_API_KEY");

All requests will be made over an encrypted HTTPS connection.

You can instruct the API client to make all requests over an HTTP proxy. Set the URL of your proxy server, which can optionally include credentials.

\Tinify\setProxy("http://user:pass@192.168.0.1:8080");

Compressing images

You can upload any AVIF, WebP, JPEG or PNG image to the Tinify API to compress it. We will automatically detect the type of image and optimise with the TinyPNG or TinyJPG engine accordingly. Compression will start as soon as you upload a file or provide the URL to the image.

You can choose a local file as the source and write it to another file. 

$source = \Tinify\fromFile("unoptimized.webp");
$source->toFile("optimized.webp");

You can also upload an image from a buffer (a string with binary) and get the compressed image data. 

$sourceData = file_get_contents("unoptimized.jpg");
$resultData = \Tinify\fromBuffer($sourceData)->toBuffer();

You can provide a URL to your image instead of having to upload it. 

$source = \Tinify\fromUrl("https://tinypng.com/images/panda-happy.png");
$source->toFile("optimized.png");

Resizing images

Use the API to create resized versions of your uploaded images. By letting the API handle resizing you avoid having to write such code yourself and you will only have to upload your image once. The resized images will be optimally compressed with a nice and crisp appearance.

You can also take advantage of intelligent cropping to create thumbnails that focus on the most visually important areas of your image.

Resizing counts as one additional compression. For example, if you upload a single image and retrieve the optimized version plus 2 resized versions this will count as 3 compressions in total.

To resize an image, call the resize method on an image source:

$source = \Tinify\fromFile("large.jpg");
$resized = $source->resize(array(
    "method" => "fit",
    "width" => 150,
    "height" => 100
));
$resized->toFile("thumbnail.jpg");

The method describes the way your image will be resized. The following methods are available:

Scale
scale
Scales the image down proportionally. You must provide either a target width or a target height, but not both. The scaled image will have exactly the provided width or height.
Fit
fit
Scales the image down proportionally so that it fits within the given dimensions. You must provide both a width and a height. The scaled image will not exceed either of these dimensions.
Cover
cover
Scales the image proportionally and crops it if necessary so that the result has exactly the given dimensions. You must provide both a width and a height. Which parts of the image are cropped away is determined automatically. An intelligent algorithm determines the most important areas of your image.
Thumb
thumb
A more advanced implementation of cover that also detects cut out images with plain backgrounds. The image is scaled down to the width and height you provide. If an image is detected with a free standing object it will add more background space where necessary or crop the unimportant parts. This feature is new and we’d love to hear your feedback!

If the target dimensions are larger than the original dimensions, the image will not be scaled up. Scaling up is prevented in order to protect the quality of your images.

Converting images

You can use the API to convert your images to your desired image type. Tinify currently supports converting between AVIF, WebP, JPEG, and PNG. When you provide more than one image type in your convert request, the smallest version will be returned to you.

Image converting will count as one additional compression.

$source = \Tinify\fromFile("panda-sticker.jpg");
$converted = $source->convert(array("type" => ["image/webp","image/png"]));
$extension = $converted->result()->extension();
$converted->toFile("panda-sticker." . $extension);

Images with transparency

Images with a transparent background will only be converted to formats that support transparency. In case you want to include formats that do not support transparency (JPEG), one can specify a background color that replaces the transparency using the transform object.

If you wish to convert an image with a transparent background to one with a solid background, specify a background property in the transform object. If this property is provided, the background of a transparent image will be filled.

$source = \Tinify\fromFile("panda-sticker.png");
$converted = $source->convert(array("type" => "image/jpeg"))->transform(array("background" => "#000000"));
$converted->toFile("panda-sticker.jpg");

Request options

You can provide the following options to convert your image:

convert
Your desired image types. The following options are available as a type:
  • One image type, specified as a string "image/webp".
  • Multiple image types, specified as an array ["image/webp","image/png"]. The smallest of the provided image types will be returned.
  • The wildcard "*/*" returns the smallest of Tinify's supported image types, currently AVIF, WebP, JPEG and PNG.
transform
The transform object specifies the stylistic transformations that will be applied to your image. Include a background property to fill a transparent image's background. The following options are available to specify a background color:
  • A hex value. Custom background color using the color's hex value: "#000000".
  • "white" or "black". Only the colors white and black are supported as strings.
You must specify a background color if you wish to convert an image with a transparent background to an image type which does not support transparency (like JPEG).

Preserving metadata

You can request that specific metadata is copied from the uploaded image to the compressed version. Preserving copyright information, the GPS location and the creation date are currently supported. Preserving metadata adds to the compressed file size, so you should only preserve metadata that is important to keep.

Preserving metadata will not count as an extra compression. However, in the background the image will be created again with the additional metadata.

To preserve specific metadata, call the preserve method on an image source:

$source = \Tinify\fromFile("unoptimized.jpg");
$copyrighted = $source->preserve("copyright", "creation");
$copyrighted->toFile("optimized-copyright.jpg");

You can provide the following options to preserve specific metadata. No metadata will be added if the requested metadata is not present in the uploaded image.

copyright
Preserves any copyright information. This includes the EXIF copyright tag (JPEG), the XMP rights tag (PNG) as well as a Photoshop copyright flag or URL. Uses up to 90 additional bytes, plus the length of the copyright data.
creation
Preserves any creation date or time. This is the moment the image or photo was originally created. This includes the EXIF original date time tag (JPEG) or the XMP creation time (PNG). Uses around 70 additional bytes.
location (JPEG only)
Preserves any GPS location data that describes where the image or photo was taken. This includes the EXIF GPS latitude and GPS longitude tags (JPEG). Uses around 130 additional bytes.

Saving to Amazon S3

You can ask the Tinify API to save compressed images straight to your Amazon S3. This feature is useful if you use S3 for images hosting, eliminating the need to download them to your server and manually upload them to S3. Each upload will be counted as an additional compression.

To save an image to S3, call the store method on an image source:

$source = \Tinify\fromFile("unoptimized.jpg");
$source->store(array(
    "service" => "s3",
    "aws_access_key_id" => "AKIAIOSFODNN7EXAMPLE",
    "aws_secret_access_key" => "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY",
    "region" => "us-west-1",
    "headers" => array("Cache-Control" => "max-age=31536000, public"),
    "path" => "example-bucket/my-images/optimized.jpg"
));

You need to provide the following options in order to save an image on Amazon S3:

service
Specify s3 to store to Amazon S3.
aws_access_key_id
aws_secret_access_key
Your AWS access key ID and secret access key. These are the credentials to an Amazon AWS user account. Find out how to obtain them in Amazon’s documentation. The user must have the correct permissions, see below for details.
region
The AWS region in which your S3 bucket is located.
path
The path at which you want to store the image including the bucket name. The path must be supplied in the following format: <bucket>/<path>/<filename>.

The following settings are optional:

headers (experimental)
You can add a Cache-Control header to control browser caching of the stored image, with for example: public, max-age=31536000. The full list of directives can be found in the MDN web docs.
acl (optional)
Set an optional Access Control List (ACL) value to manage object accessibility. By default, objects are set to public-read. Use no-acl to prevent sending an ACL. For more information about ACL options, refer to the AWS Canned ACL documentation.

The user that corresponds to your AWS access key ID must have the PutObject and PutObjectAcl permissions on the paths of the objects you intend to create.

Example S3 access policy

If you want to create a user with limited access specifically for the Tinify API, you can use the following example policy as a starting point:

{
  "Statement": {
    "Effect": "Allow",
    "Action": [
      "s3:PutObject",
      "s3:PutObjectAcl"
    ],
    "Resource": [
      "arn:aws:s3:::example-bucket/*"
    ]
  }
}

Saving to Google Cloud Storage

You can tell the Tinify API to save compressed images directly to Google Cloud Storage. If you use GCS to host your images this saves you the hassle of downloading images to your server and uploading them to GCS yourself. Each upload will be counted as an additional compression.

Before you can store an image in GCS you will need to generate an access token with a service account.

We still need to create a piece of example code for this language that generates an access code. In case you have a working example ready, please share your code!

Once you have generated the access token you can then save the optimised image directly to GCS by calling the store method on an image source:

$source = \Tinify\fromFile("unoptimized.jpg");
$source->store(array(
    "service" => "gcs",
    "gcp_access_token" => "EXAMPLE_TOKEN_Ag_0HvsglgriGh5_EXAMPLE_TOKEN",
    "headers" => array("Cache-Control" => "max-age=31536000, public"),
    "path" => "example-bucket/my-images/optimized.jpg"
));

You need to provide the following options in order to save an image on Google Cloud Storage:

service
Specify gcs to store to Google Cloud Storage.
gcp_access_token
The access token for authenticating to Google's Cloud Platform. Find out how to generate these tokens with the example above.
path
The path at which you want to store the image including the bucket name. The path must be supplied in the following format: <bucket>/<path>/<filename>.

The following settings are optional:

headers (experimental)
You can add a Cache-Control header to control browser caching of the stored image, with for example: public, max-age=31536000. The full list of directives can be found in the MDN web docs.

Saving to S3 compatible storage

Although the TinyPNG API does not offer an integrated solution for saving the images directly to S3 compatible storage providers other than Amazon, you can still save your images using the example for your chosen development language.

The S3 API is used by storage providers like Digital Ocean Spaces, Backblaze, G-Core Storage, Wasabi, Century Link Object Storage, Filebase and many others.

If you don’t have the AWS SDK installed already, you can add it using the following command:

composer require aws/aws-sdk-php

Store example

$source = \Tinify\fromUrl("https://tinypng.com/images/panda-happy.png");
$resultData = $source->toBuffer();

$client = new Aws\S3\S3Client([
  'version' => 'latest',
  'region'  => 'REGION',
  'endpoint' => 'https://YOUR-ENDPOINT.com',
  'credentials' => [
          'key'    => "KEY_EXAMPLE",
          'secret' => "YOUR_SECRET_KEY",
      ],
]);

$client->putObject([
  'Bucket' => 'bucket-name',
  'Key'    => 'file-name.png',
  'Body'   => $resultData,
  'ContentType' => 'image/png'
]);

The detailed documentation on how to use the S3 API can be found here.

Saving to Microsoft Azure

Although the TinyPNG API does not offer an integrated solution for saving the images directly to Microsoft Azure storage, you can still save your images using the example for your chosen development language.

Keep in mind you will need to install the Azure Storage package using the following command:

composer require Microsoft/azure-storage-blob

Store example

The following example explains how to connect to your blob container and upload your image, using your Azure storage connection string. Your connection string can be found on your Azure storage dashboard.

$connectionString = '<YOUR_AZURE_STORAGE_CONNECTION_STRING>';
$blobClient = BlobRestProxy::createBlobService($connectionString);

$containerName = '<YOUR_CONTAINER_NAME>';
$blobClient->getContainer(strtolower($containerName));

$fileToUpload = "optimized.png";
$source = \Tinify\fromUrl("https://tinypng.com/images/panda-happy.png");
$source->toFile($fileToUpload);


$content = fopen($fileToUpload, "r");
$blobClient->createBlockBlob($containerName, $fileToUpload, $content);

The detailed documentation on how to use the Azure storage API can be found here.

Error handling

The Tinify API uses HTTP status codes to indicate success or failure. Any HTTP errors are converted into exceptions, which are thrown by the client library.

There are four distinct types of errors. The exception message will contain a more detailed description of the error condition.

AccountException
There was a problem with your API key or with your API account. Your request could not be authorized. If your compression limit is reached, you can wait until the next calendar month or upgrade your subscription. After verifying your API key and your account status, you can retry the request. In case of a rate limit exceeded error, please add some delay to consecutive requests. Tinify has a generous rate limit to ensure a high quality of service to all clients.
ClientException
The request could not be completed because of a problem with the submitted data. The exception message will contain more information. You should not retry the request.
ServerException
The request could not be completed because of a temporary problem with the Tinify API. It is safe to retry the request after a few minutes. If you see this error repeatedly for a longer period of time, please contact us.
ConnectionException
The request could not be sent because there was an issue connecting to the Tinify API. You should verify your network connection. It is safe to retry the request.

You can handle each type of error separately:

try {
    // Use the Tinify API client.
} catch(\Tinify\AccountException $e) {
    print("The error message is: " . $e->getMessage());
    // Verify your API key and account limit.
} catch(\Tinify\ClientException $e) {
    // Check your source image and request options.
} catch(\Tinify\ServerException $e) {
    // Temporary issue with the Tinify API.
} catch(\Tinify\ConnectionException $e) {
    // A network connection error occurred.
} catch(Exception $e) {
    // Something else went wrong, unrelated to the Tinify API.
}

If you are writing code that uses an API key configured by your users, you may want to validate the API key before attempting to compress images. The validation makes a dummy request to check the network connection and verify the API key. An error is thrown if the dummy request fails.

try {
    \Tinify\setKey("YOUR_API_KEY");
    \Tinify\validate();
} catch(\Tinify\Exception $e) {
    // Validation of API key failed.
}

Compression count

The API client automatically keeps track of the number of compressions you have made this month. You can get the compression count after you have validated your API key or after you have made at least one compression request.

$compressionsThisMonth = \Tinify\compressionCount();

Need help? Got feedback?

We’re always here to help, so if you’re stuck just drop us a note on support@tinify.com. It’s also the perfect place to send us all your suggestions and feedback.

Try TinyPNG with a new browser

TinyPNG is created for modern browsers with HTML5 & CSS3 support. We have not tried it out in other browsers. The site may work, or it may not. If you see this message you may want to try a different browser!