Complete image solution

After creating your account, you add your web site as a site configuration and get an Image CDN Base URL which is something like https://img.synaps.pics/your-site/. This URL represents the root path for you web site images. If you have an image on your web site with URL like https://example.com/https://img.synaps.pics/synaps/pics/landing/images/nature.jpg, you should convert it to https://img.synaps.pics/your-site/https://img.synaps.pics/synaps/pics/landing/images/nature.jpg and synaps.pics will automatically optimize that image on-fly.

You can customize configuration of this set up. Even by using our Custom Domain feature you can use your domain/subdomain to serve optimized images.

If you want to scale images or use any other image processing feature, you can easily add transformation parameters to image URL like : https://img.synaps.pics/your-site/w_300,h_200,c_fill,q_75/https://img.synaps.pics/synaps/pics/landing/images/nature.jpg

We also provide SDK libraries and plugins for various programming languages, frameworks and systems. These libraries can automatically modify your existing image links to serve them over synaps.pics.

Please check our documentation for detailed examples and information.

Uploading your images to our Image Storage solution is not necessary if you want to store and maintain your images on your server. Image Storage solution is an optional feature. It provides highly-available, reduntant and fast image storage service. By using the image storage, you can reduce the disk space needed for your project and get rid of the cost of any backup solution for your images.

If you are using AWS S3 or similar cloud storage services, by switching to our storage solution you can gain speed and reduce your costs. Please refer to the documentation for detailed explaination about how our image storage solution works.

We have 2 pricing methods : pay-as-you-go (PAYG) and plans. If you choose PAYG method, you'll be billed for every individual feature which has own separate PAYG pricing as you use them. For example, in a month if you use 10 GB of bandwidth and 10k transformations, you will be billed as :

10 GB x $0.28 = $2.8
10,000 x $0.00009 = $0.9
Total : $2.8 + $0.9 = $3.7

In PAYG, if you use any additional solution it will also be added to monthly bill. For example, if you use custom domain feature which has a fix monthly price, your monthly bill will also have $5 x number of custom domains.

PAYG model gives you more control over your monthly bill, if you are not using all of features included in plans or you don't need discounts provided in plans.

If you choose to go with plans, you'll be billed the total price of the selected plan at the end of the month, even you don't use all the features and capacity that a plan contains. For any extra usage, you will also billed for the extras you used.

For example, if you choose the Basic Plan and if your service usage is within the limits of the plan, you will be charged with $10/month. But if you also use a custom domain with the basic plan, your bill will also include the PAYG pricing for the custom domain.

Every pre-defined plan has a total discount on service usage pricing. If any plan limits is suitable for your project, it is better you to choose plans because probably it will cost less than PAYG model if you use all features a plan provides.

Please refer to our pricing documentation for other details and examples on pricing.

Synaps.pics servers sit between your web site visitors and your server / image origin. When an image is requested by any visitor of your web site, we serve it instead of your server, in an optimized format based on your settings. So, when an image requested from our system, it automatically counts the file size of optimized image file and adds it to your bandwidth usage.

Because we only serve optimized images and count file sizes of optimized images while calculating bandwidth usage, you don't have to worry about original file sizes of your images. We don't charge for any bandwidth which occurs while pulling original files from your server to our system.

The transformation is the any image processing operation that our backend systems do for the features like optimizing, scaling, transforming, converting, croping, etc. After any transformation operation the resulted image is cached on our servers not to process images again with same parameters. So, normally any transformation operation occurs only once if the same set of processing parameters is used.

Synaps.pics also process images once even you don't specify any custom image parameter in the image URL. Even there is no image processing parameter, we at least optimize the image file by compressing it with suitable configuration methods and default optimization settings. This optimization operation is also done only once and cached but it also increment the number of transformations done.

For example, suppose that you have `https://img.synaps.pics/synaps/pics/landing/images/nature.jpg` file as original file. When it is first served from `https://img.synaps.pics/your-site/https://img.synaps.pics/synaps/pics/landing/images/nature.jpg`, we optimize the original image and save it to our cache. So, transformation count is incremented by 1. Successive requests to the same URL does not trigger any transformation if you don't use advanced HTTP header based image processing options.

If you want to scale the image by specifying a width parameter like `https://img.synaps.pics/your-site/w_300/https://img.synaps.pics/synaps/pics/landing/images/nature.jpg` then it will again trigger another transformation and the transformation count will incremented by 1. But again because this URL will also be cached on our servers, accessing the same URL won't cause any transformation (unless you use HTTP header based techniques for especially automatic Webp support).

When a CDN is placed in front of your origin server, it generally request the original content multiple times because generally CDN caches are placed in regional locations. So, if CDN has 30 regional edge cache servers, the same file is requested for 30 times from the origin server. For that reason, bandwidth saving on the origin server network might be limited.

Synaps.pics has many edge servers for its CDN all over the world. To help our customers to reduce their origin server bandwidth usage to its minimum, we use a special master caching server to request the original image only once even it is served from different geographical regions with our CDN edge servers. This is called as Origin Shield which prevents additional requests to the same file from the origin within the cache TTL period.

Origin shield is custom feature which is enabled manually. Origin shield can save you from lots of HTTP requests and excessive bandwidth usage. Basically, with origin shield, your origin server will serve any image for once within cache TTL period.