Starting in mid-August, Scryfall will be transitioning our image and data origins to new subdomains. Images and bulk data items will stop being hosted on img.scryfall.com and archive.scryfall.com and they will move to new federated hosts at c1.scryfall.com, c2.scryfall.com , c3.scryfall.com, and so on, with new file paths.
Why are you doing this?
Scryfall is transitioning to a new file hosting provider to improve our scalability and also save money.
Will this break my existing code?
Only if you’ve been naughty. We don’t recommend that you ever try to manually construct a link to a file on img.scryfall.com or archive.scryfall.com. Instead you should fetch card data using our API or bulk file offerings, those objects always include the correct and up-to-date URI to card images and downloadable files.
As a reminder:
- If you want to download a card’s image using its set code and collector number, use the /cards/:code/:number method and specify the
format=imageoption. You will receive an HTTP redirect to the correct file. - If you want to download a card’s image using its Scryfall ID, use the /cards/:id endpoint and specify the
format=imageoption. You will receive an HTTP redirect to the correct file. - If you want to bookmark a direct link to a bulk data item, use the /bulk-data/:type method and specify the
format=fileoption. You will receive an HTTP redirect right to the latest bulk data file of that type.
If you have already been using the API to retrieve image and file URIs, nothing should change for you.
Will this affect any api.scryfall.com method paths?
No, this only affects our file download hosts and the URIs found in image_uris and download_uri and similar fields inside API objects.
Will this affect projects I have that use CORS?
No, the new origins should function the same with Cross Origin Resource Sharing.
What if I have cached the old links? Will you set up any redirects?
Yes, we will be creating redirects for img.scryfall.com and archive.scryfall.com, but you should not permanently rely on these redirects. They should be considered temporary band-aids until you are able to update anything affected by the domain changes.
Can I still hotlink to the new origins?
Yes.
Do the new origins have a rate limit?
No, only api.scryfall.com has a rate limit.
Questions?
If you need additional clarification on any of these changes, please don’t hesitate to contact us