Scryfall Changelog

Changelog Feed

High-resolution PNG images

When available, card profiles now include a link to download a full-resolution PNG image with rounded corners and transparent edges. These images are designed for tasks that need the best quality assets, such as videos and promotional art.

In the toolbox section of card profile pages, click the “Download PNG image” link. Examples:

These image files are also now returned via the API, in the image_uris object.

“Appeared in” set filter

You can now use the in: or wasin: keyword to filter cards based on a set they β€œappeared in”, but not otherwise require that set in results.

Examples of interesting searches you can make with this keyword:

Previously this functionality was available using the e:set+set or e:set,* syntaxes. Use the in: keyword instead for official support.

High resolution images

Scryfall is rolling out support for high resolution card images. We currently have all of Standard available, and new sets are being added daily.

For developers: Card objects in the API now have an image_uris property, which will be populated with different image sizes if the card in question has high-res imaging available. Note that many cards (especially promos) will not have these fields available immediately. You should handle both situations in your code.

We hope you really enjoy this update. We want to support content creators, app builders, and anyone else that needs high-resolution images to do their work. Please let us know what you think! πŸš€

Feedback and ticketing

We wanted to streamline the process of collecting your feedback, and to give you the opportunity to participate in any conversation that follows your report. So, we’ve added a feedback form to the site that will open a new ticket in our official feedback tracker.

Once you’ve submitted a feedback report, you’ll be provided with a link to your newly opened ticket. Check that link at any time to follow your ticket status, or better yet, sign up for a free GitHub account so that you can subscribe to notifications and leave additional comments.

We thank you all for the feedback you’ve sent us to date concerning card issues and the website itself. Keep it coming!

Split & flip cards updated

Split and flip cards have been updated. Each half of the card has been combined into a single page. Information for split cards has been updated to adhere to the Amonkhet rules update. Notably:

Split/Flip Card Search Updates

The search system now understands that a split/flip card has one combined name like Beck//Call but also two distinct names, Beck and Call. You can now search for one or both halves of a split card using any of these formats.

Split/Flip Card Changes for Bots

The Slack and Discord bots now understand requests for split card names, such as [[Wear//Tear]].

API Changes for Split/Flip Cards

Each split and flip card is now represented as a single object via the API instead of two. A new card_faces property has been added that contains information for each half of the split/flip card. See the updated API documentation for details.

Notice of upcoming changes to images, split cards, and flip cards

This post is to provide advance warning to developers that Scryfall’s data model will soon change how we present split cards, flip cards, and card images. The changes will unfortunately be backwards-incompatible with the previous API.

High-Resolution Images

We will be slowly rolling out higher resolution images for cards!

πŸ‘‡ Click to ENHANCE.

  • Our current cards are available at 336Γ—469px.
  • New images will be double that size, at 672Γ—938px. 😱😍

A new field images will be added to the card object with normal and large properties with URIs to each version.

The image property will continue pointing to the normal version of the image, but is now deprecated.

Not all cards will have high-res images immediately. This change will likely creep out to newer sets and expansion sets first, then to all supplemental sets. When a card doesn’t have a high-res image, its images.large property will be null.

The system we’re building to make this change opens up a bunch of future possibilities with card images: art crops, square crops, consistently rounded corners, and more. Let us know what you want to see out of this. Stay tuned!

Split Cards and Flip Cards

Because users so often search for the combined name of split cards or search “across” the two halves of split cards (to discover casting loopholes, etc) we will be combining split cards and flip cards into a single object representing both halves of the card.

  • The name field for a split/flip card object will contain both names of the card. For example Wear // Tear
  • The mana_cost field for a split/flip card object will contain both values on the card. For example {1}{R} // {W}
  • A new faces field will contain two card_face objects that will have the distinct name, mana_cost, type_line, oracle_text, power, and toughness information for each face of the split/flip card.
  • The parent-level fields type_line, oracle_text, power, and toughness will be null for split/flip cards.
  • Other parent fields such as multiverse_id, prices, set information, etc will be unchanged.

These new combined card objects will replace the previous left-side/top-side object in our results. The object for the other side will be deleted.

  • For example, our current object for DGM Wear has ID d169a3b2… and the object for DGM Tear has ID bd0f7a22…. When this update occurs there will be only one object with ID d169a3b2… called Wear // Tear.

We will be updating split cards to adhere to the new Magic rules update:

  • The converted_mana_cost will now be the sum of the converted mana cost of both halves.
  • The color will now be the union of the colors of both halves.
  • The color_identity will now be the union of the color identity of both halves.

When searching for split/flip cards, API endpoints that use either part of the name or the combined // name will work:

  • Searching for a card named exactly Wear will find Wear // Tear.
  • Searching for a card named exactly Tear will find Wear // Tear.
  • Searching for cards named Wear/Tear, Wear // Tear, or Wear //\\/\/ Tear will find Wear // Tear.
  • Partial name searches will now match either side of the card or both. For example searching for we tea will now include Wear // Tear.

In addition, our chat bots will now return both halves of a split/flip card when you search for one or both sizes. For example [[Wear]] and [[Wear//Tear]] will now find Wear // Tear.

Transform and meld cards are unaffected by this update. They will remain distinct cards with an all_parts field as usual.

Thank you!

Thank you so much from the bottom of our hearts for using our API. We’ve been delighted by the things we’re seeing people build. If you have any questions or feedback about these changes, please send us a message.

Regular expression keyword now available

The re: or regex: operator is now available to filter Oracle text using a regular expression.

Regular expressions are very powerful. Here are some examples of searches you can make with this keyword:

Please see our syntax guide and full regex documentation page for all the details.

Search Future Standard

We’ve added a new “format”: future. Using the f:future keyword or picking “Future Standard” on the advanced search will let you search over what Standard will be once the next set is released or a rotation occurs. Whenever we start spoiling a new Standard set, we will update f:future to let you brew for the coming season.

Try it out with f:future to brew with Amonkhet.

New format keyword shortcuts

Additional shorthand is available for the f:/format: keyword.

Early sets renumbered

Many older sets have been renumbered to more closely match the standardized color/name order that newer sets usually have.

Note that none of the following sets have official collector numbers, so our re-assigned numbers continue to be chosen “arbitrarily” and/or not from WOTC:

In addition, the following sets were renumbered to match either the partial or full list of collector numbers we have for that set from Magic Online. The rest of the set numbers were assigned “arbitrarily” as with the above list.

October bugfix update

We fixed a lot of bugs and small omissions thanks to everyone who reported issues on release day, including:

  • Searches for t:assembly-worker now work correctly
  • Fixed incorrect Vintage legality results
  • Fixed incorrect Clash Pack images
  • Repaired a few URL format inconsistencies in API results
  • Fixed lots of spelling errors