Skip to content PHP SDK
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
sample fix: failing chained transformtion #6 Feb 5, 2020
src/ImageKit fix: failing chained transformtion #6 Feb 5, 2020
LICENSE chore: Initial setup Jan 17, 2020
composer.json Doc fix Feb 7, 2020
composer.lock chore: fix links in readme & update composer lock Feb 7, 2020

PHP SDK for ImageKit

PHP CI Packagist Packagist License: MIT Twitter Follow

PHP SDK for ImageKit that implements the new APIs and interface for performing different file operations.

ImageKit is a complete image optimization and transformation solution that comes with and image CDN and media storage. It can be integrated with your existing infrastructure - storages like AWS s3, web servers, your CDN and custom domain names, allowing you to deliver optimize images in minutes with minimal code changes.

Table of contents -


Go to your terminal and type the following command

composer require imagekit/imagekit


use ImageKit\ImageKit;

$imageKit = new ImageKit(


You can use this PHP SDK for 3 different kinds of methods - URL generation, file upload and file management. The usage of the SDK has been explained below

URL generation

1. Using Image path and image hostname or endpoint

This method allows you to create a URL using the path where the image exists and the URL endpoint(url_endpoint) you want to use to access the image. You can refer to the documentation here to read more about URL endpoints in ImageKit and the section about image origins to understand about paths with different kinds of origins.

$imageURL = $imageKit->url(array(
    "path" => "/default-image.jpg",
    "transformation" => array(
            "height" => "300",
            "width" => "400",

The result in a URL like,w-400/default-image.jpg

2.Using full image URL This method allows you to add transformation parameters to and existing, complete URL that is already mapped to ImageKit using src parameter. This method should be used if you have the complete image URL mapped to ImageKit stored in your database.

$imageURL = $imageKit->url(array(
    "src" => "",     
    "transformation" => array(
            "height" => "300",
            "width" => "400",

This results in a URL like

The $imageKit->url() method accepts the following parameters

Option Description
urlEndpoint Optional. The base URL to be appended before the path of the image. If not specified, the URL Endpoint specified at the time of SDK initialization is used. For example,
path Conditional. This is the path at which the image exists. For example, /path/to/image.jpg. Either the path or src parameter need to be specified for URL generation.
src Conditional. This is the complete URL of an image already mapped to ImageKit. For example, Either the path or src parameter need to be specified for URL generation.
transformation Optional. An array of objects specifying the transformation to be applied in the URL. The transformation name and the value should be specified as a key-value pair in the object. Different steps of a chained transformation can be specified as different objects of the array. The complete list of supported transformations in the SDK and some examples of using them are given later. If you use a transformation name that is not specified in the SDK, it gets applied as it is in the URL.
transformationPostion Optional. Default value is path that places the transformation string as a path parameter in the URL. Can also be specified as query which adds the transformation string as the query parameter tr in the URL. If you use src parameter to create the URL, then the transformation string is always added as a query parameter.
queryParameters Optional. These are the other query parameters that you want to add to the final URL. These can be any query parameters and not necessarily related to ImageKit. Especially useful, if you want to add some versioning parameter to your URLs.
signed Optional. Boolean. Default is false. If set to true, the SDK generates a signed image URL adding the image signature to the image URL. This can only be used if you are creating the URL with the urlEndpoint and path parameters, and not with the src parameter.
expireSeconds Optional. Integer. Meant to be used along with the signed parameter to specify the time in seconds from now when the URL should expire. If specified, the URL contains the expiry timestamp in the URL and the image signature is modified accordingly.

Examples of generating URLs

1. Chained Transformations as a query parameter

$imageURL = $imageKit->url(array(
    "path" => "/default-image.jpg",
    "url_endpoint" => "",
    "transformation" => array(
            "height" => "300",
            "width" => "400",
            "rotation" => 90
    "transformationPosition" => "query"

2. Sharpening and contrast transforms and a progressive JPG image

There are some transforms like Sharpening that can be added to the URL with or without any other value. To use such transforms without specifying a value, specify the value as "-" in the transformation object, otherwise, specify the value that you want to be added to this transformation.

$imageURL = $imageKit->url(array(
    "src" => "",
    "transformation" => array(
            "format" => "jpg",
            "progressive" => "true",
            "effectSharpen" => "-",
            "effectContrast" => "1"
//Note that because `src` parameter was used, the transformation string gets added as a query parameter `tr`

3. Signed URL that expires in 300 seconds with the default URL endpoint and other query parameters

 $imageURL = $imageKit->url(array(
    "path" => "/default-image.jpg",
    "queryParameters" => array(
        "v" => "123",        
    "transformation" => array(
            "height" => "300",
            "width" => "400" 
    "signed" => true,
    "expireSeconds" => 300,

List of supported transformations

The complete list of transformations supported and their usage in ImageKit can be found here. The SDK gives a name to each transformation parameter, making the code simpler and readable. If a transformation is supported in ImageKit, but a name for it cannot be found in the table below, then use the transformation code from ImageKit docs as the name when using in the url function.

Supported Transformation Name Translates to parameter
height h
width w
aspectRatio ar
quality q
crop c
cropMode cm
x x
y y
focus fo
format f
radius r
background bg
border bo
rotation rt
blur bl
named n
overlayImage oi
overlayX ox
overlayY oy
overlayFocus ofo
overlayHeight oh
overlayWidth ow
overlayText ot
overlayTextFontSize ots
overlayTextFontFamily otf
overlayTextColor otc
overlayAlpha oa
overlayTextTypography ott
overlayBackground obg
overlayImageTrim oit
progressive pr
lossless lo
trim t
metadata md
colorProfile cp
defaultImage di
dpr dpr
effectSharpen e-sharpen
effectUSM e-usm
effectContrast e-contrast
effectGray e-grayscale
original orig

File Upload

The SDK provides a simple interface using the $imageKit->upload() method to upload files to the ImageKit Media Library. It accepts all the parameters supported by the ImageKit Upload API.

The upload() method requires at least the file and the fileName parameter to upload a file and returns a callback with the error and result as arguments. You can pass other parameters supported by the ImageKit upload API using the same parameter name as specified in the upload API documentation. For example, to specify tags for a file at the time of upload use the tags parameter as specified in the documentation here.

Sample usage

    'file' => "your_file",
    'fileName' => "your_file_name.jpg",

Available options for request



file required

This field accepts three kinds of values: - binary - You can send the content of the file as binary. This is used when a file is being uploaded from the browser. - base64 - Base64 encoded string of file content. - url - URL of the file from where to download the content before uploading. Downloading file from URL might take longer, so it is recommended that you pass the binary or base64 content of the file. Pass the full URL, for example -

file_name required

The name with which the file has to be uploaded.

use_unique_file_name optional

Whether to use a unique filename for this file or not. - Accepts true or false. - If set true, will add a unique suffix to the filename parameter to get a unique filename. - If set false, then the image is uploaded with the provided filename parameter and any existing file with the same name is replaced. Default value - true

tags optional

Set the tags while uploading the file. - Comma-separated value of tags in format tag1,tag2,tag3. For example - t-shirt,round-neck,men - The maximum length of all characters should not exceed 500. - % is not allowed. - If this field is not specified and the file is overwritten then the tags will be removed.

folder optional

The folder path (e.g. /images/folder/) in which the image has to be uploaded. If the folder(s) didn't exist before, a new folder(s) is created. The folder name can contain: - Alphanumeric Characters: a-z , A-Z , 0-9 - Special Characters: /``_ and - - Using multiple / creates a nested folder. Default value - /

is_private_file optional

Whether to mark the file as private or not. This is only relevant for image type files. - Accepts true or false. - If set true, the file is marked as private which restricts access to the original image URL and unnamed image transformations without signed URLs. Without the signed URL, only named transformations work on private images Default value - false

custom_coordinates optional

Define an important area in the image. This is only relevant for image type files.

  • To be passed as a string with the x and y coordinates of the top-left corner, and width and height of the area of interest in format x,y,width,height. For example - 10,10,100,100

  • Can be used with fo-customtransformation.

  • If this field is not specified and the file is overwritten, then customCoordinates will be removed.

response_fields optional

Comma-separated values of the fields that you want to return in response. For example, set the value of this field to tags,custom_coordinates,is_privateFile,metadata to get value of tags, custom_coordinates, is_privateFile , and metadata in the response.

If the upload succeed, error will be null and the result will be the same as what is received from ImageKit's servers. If the upload fails, error will be the same as what is received from ImageKit's servers and the result will be null.

File Management

The SDK provides a simple interface for all the media APIs mentioned here to manage your files. You can use a callback function with all API interfaces. The first argument of the callback function is the error and the second is the result of the API call. Error will be null if the API succeeds.

1. List & Search Files

Accepts an object specifying the parameters to be used to list and search files. All parameters specified in the documentation here can be passed as is with the correct values to get the results.


2. Get File Details

Accepts the file ID and fetches the details as per the API documentation here.


3. Get File Metadata

Accepts the file ID and fetches the metadata as per the API documentation here.


4. Get File Metadata from remote URL

Accepts the file ID and fetches image exif, pHash and other metadata from powered remote URL as per the API documentation here.


5. Update File Details

Update parameters associated with the file as per the API documentation here. The first argument to the updateFileDetails method is the file ID and the second argument is an object with the parameters to be updated.

$imageKit->updateFileDetails("file_id", array("tags" => ['image_tag']));

6. Delete File

Delete a file as per the API documentation here. The method accepts the file ID of the file that has to be deleted.


7. Delete Bulk Files by ID

Deletes multiple files and all their transformations as per the API documentation here. The method accepts the array of file IDs that has to be deleted.

    "fileIds" => ["file_id_1", "file_id_2", ...]

8. Purge Cache

Programmatically issue a cache clear request as per the API documentation here. Accepts the full URL of the file for which the cache has to be cleared.


9. Purge Cache Status

Get the purge cache request status using the request ID returned when a purge cache request gets submitted as per the API documentation here


Utility functions

We have included following commonly used utility functions in this package.

Authentication parameter generation

In case you are looking to implement client-side file upload, you are going to need a token, expiry timestamp and a valid signature for that upload. The SDK provides a simple method that you can use in your code to generate these authentication parameters for you.

Note: The Private API Key should never be exposed in any client-side code. You must always generate these authentication parameters on the server-side

$imageKit->getAuthenticationParameters($token = "", $expire = 0);


    "token" => "unique_token",
    "expire" => "valid_expiry_timestamp",
    "signature" => "generated_signature",

Both the token and expire parameters are optional. If not specified the SDK uses the uuid package to generate a random token and also generates a valid expiry timestamp internally. The value of the token and expire used to generate the signature are always returned in the response, no matter if they are provided as an input to this method or not.

Distance calculation between two pHash values

Perceptual hashing allows you to constructing a hash value that uniquely identifies an input image based on the contents of an image. metadata API returns the pHash value of an image in the response. You can use this value to find a duplicate (or similar) image by calculating distance between pHash value of two images.

This SDK exposes pHashDistance function to calcualte distance between two pHash values. It accepts two pHash hexadecimal strings and returns a numeric value indicative of the level of difference between the two images.

  $imageKit->pHashDistance($firstHash ,$secondHash);    

Distance calculation examples

$imageKit->pHashDistance('f06830ca9f1e3e90', 'f06830ca9f1e3e90');
// output: 0 (same image)

$imageKit->pHashDistance('2d5ad3936d2e015b', '2d6ed293db36a4fb');
// output: 17 (similar images)

$imageKit->pHashDistance('a4a65595ac94518b', '7838873e791f8400');
// output: 37 (dissimilar images)


For any feedback or to report any issues or general implementation support please reach out to



Released under the MIT license.

You can’t perform that action at this time.