Switching to FileSpin / Replace an image or video API

Replace an image or video API

Replace your image or video API with a library your whole team can use.

Moving from Cloudinary, ImageKit, imgix, Cloudflare or ImageEngine? FileSpin creates image sizes and formats from a URL, streams video and delivers through a CDN, from the same library your content team searches, reviews and shares from.

Book a demo to talk through your image and video delivery with our team. Start a free trial – no credit card required.

Illustration: a media library whose images and video are delivered at the sizes each channel needs, with delivery figures, for developers and the content team.

What you keep

Your sites and apps keep getting every image size and video stream they need.

Your developers keep working with URLs, APIs and webhooks. The originals stay in your library.

Image sizes and formats from a URL

Create the size, crop and format each channel needs from a URL, with AVIF or WebP served to compatible browsers. Standard on-demand outputs don’t count against storage.

Image sizes and formats from a URL

Create the size, crop and format each channel needs from a URL, with AVIF or WebP served to compatible browsers. Standard on-demand outputs don’t count against storage.

Video processing and streaming

Turn recordings into SD and HD versions and adaptive HLS streams. Clips, posters and storyboards stay with the original.

Video processing and streaming

Turn recordings into SD and HD versions and adaptive HLS streams. Clips, posters and storyboards stay with the original.

APIs and webhooks

APIs and webhooks connect uploads, metadata and delivery to your applications, with API-key or JWT access.

APIs and webhooks

APIs and webhooks connect uploads, metadata and delivery to your applications, with API-key or JWT access.

What you gain

Your content team finds, approves and shares media themselves, and you see where it is used.

An image or video API serves your applications. FileSpin also gives your content team a library to work from, and shows how each file is delivered.

Find media by your business fields

Reusable schemas give each kind of asset its own fields, such as SKU, campaign or season. Search combines those fields with keywords, and collections group assets without copying files.

Review work and share what’s approved

Send an image or clip for internal or external review with due dates, then share approved files on branded Share Pages that show what each recipient downloaded.

See where every image and video is used

Open any image or video to see how often it is delivered and which sites embed it. Tag campaign links by channel, placement and audience to see the requests, bytes and assets delivered under each campaign.

Where you are moving from

How the move works

Each comparison sets FileSpin beside the service you use now and links to its migration guide.

Cloudinary or ImageKit

Point your delivery hostname at FileSpin.

Supported public image URLs keep working, transformations included. Images copy across the first time each one is requested, so you can check FileSpin’s output before you switch traffic.

  • Self-serve for supported public image URLs.

  • Signed URLs, video and uploads move with our tools or our team.

imgix, Cloudflare or ImageEngine

We rebuild each output and check it before cutover.

Originals come across from your sources, and the image sizes, crops and formats your pages request are rebuilt as FileSpin outputs. Your technical team runs the move with FileSpin’s tools, or the FileSpin team carries it out for you.

  • Outputs checked against the current ones.

  • Your current service keeps serving your sites while the library moves.

Every source

Metadata, video and automation move with the library.

Metadata fields and tags map to FileSpin schemas, videos and private files are transferred, and uploads and automation move to FileSpin’s APIs and webhooks.

  • Each batch is checked against the source.

  • With managed migration, the FileSpin team supports the switch.

XXL · eCommerce

150,000 retail product images migrated

While XXL’s retail websites stayed online. FileSpin now handles XXL’s product-media intake and on-demand image outputs.

150,000

images

The retail product images in XXL’s migration.

Websites online

XXL’s retail websites stayed online during the move.

Before you move

Questions about replacing an image or video API

Will our existing image URLs keep working?

Yes, for supported public Cloudinary and ImageKit image URLs. Point your delivery hostname at FileSpin and they keep working, transformations included. Coming from imgix, Cloudflare or ImageEngine, each URL your pages use is rebuilt as the matching FileSpin output and checked before cutover.

Will our existing image URLs keep working?

Yes, for supported public Cloudinary and ImageKit image URLs. Point your delivery hostname at FileSpin and they keep working, transformations included. Coming from imgix, Cloudflare or ImageEngine, each URL your pages use is rebuilt as the matching FileSpin output and checked before cutover.

Which image transformations does FileSpin cover?

Resize, crop, padding, format and quality in the URL, with AVIF or WebP served to compatible browsers. Background removal and saved AI edits prepare images before delivery. If your application composes images in the URL with layers, text overlays or conditional transformations, check a sample of those URLs in a free trial before you switch.

Which image transformations does FileSpin cover?

Resize, crop, padding, format and quality in the URL, with AVIF or WebP served to compatible browsers. Background removal and saved AI edits prepare images before delivery. If your application composes images in the URL with layers, text overlays or conditional transformations, check a sample of those URLs in a free trial before you switch.

Can we move without downtime?

Yes. Your current service keeps serving your sites while the library moves, and outputs are checked before you switch traffic.

Can we move without downtime?

Yes. Your current service keeps serving your sites while the library moves, and outputs are checked before you switch traffic.

Do we need to change our code?

Only where your application talks to your current service directly. Supported public Cloudinary and ImageKit image URLs need just the new hostname. Uploads, webhooks and other automation move to the FileSpin APIs.

Do we need to change our code?

Only where your application talks to your current service directly. Supported public Cloudinary and ImageKit image URLs need just the new hostname. Uploads, webhooks and other automation move to the FileSpin APIs.

Can FileSpin deliver our video too?

Yes, from the same library. Turn recordings into SD and HD versions, adaptive HLS streams, clips and storyboards, ready for your website, apps and partners.

Can FileSpin deliver our video too?

Yes, from the same library. Turn recordings into SD and HD versions, adaptive HLS streams, clips and storyboards, ready for your website, apps and partners.

Can we try FileSpin before we move?

Yes. Start a 30-day free trial with your own media, with no credit card needed, and see your images and video in FileSpin before you commit.

Start with your own URLs

Bring your image URLs. We’ll show you how they move across.

Tell us which service delivers your images and video today, roughly how much media there is and which sites and apps use it. In a demo, we’ll walk through how your URLs, files and metadata move to FileSpin, and who does each part.

Start with your own URLs

Bring your image URLs. We’ll show you how they move across.

Tell us which service delivers your images and video today, roughly how much media there is and which sites and apps use it. In a demo, we’ll walk through how your URLs, files and metadata move to FileSpin, and who does each part.

Start with your own URLs

Bring your image URLs. We’ll show you how they move across.

Tell us which service delivers your images and video today, roughly how much media there is and which sites and apps use it. In a demo, we’ll walk through how your URLs, files and metadata move to FileSpin, and who does each part.

Explore another route

Related solutions