Component.Studio 2 to 3 Migration

The migration completed on December 3, 2025. CS2 is no longer accessible to the public. However, you should look over your migrated games. You have until December 31 to state that there are any problems with the migration and we can re-migrate any games that have problems.

Migration Process

On Monday, December 1, 2025 we will begin migrating the hundreds of thousands of game designs you have created from Component.Studio 2 to Component.Studio 3. This process will likely take a couple of weeks as there is a lot of data to transfer. All of your existing designs will be transferred eventually. They won't be transferred in any order that would be meaningful to you, so don't worry if some of your designs have been migrated, but not all have been.

You can see which of your designs have been migrated so far by looking at: https://cs3.component.studio/games

Migrating Backups

If you have old backups of games from CS2 that don't exist anywhere other than in the backup file, and you would like those migrated to CS3, then you should import those backup files into CS2 now.  You do that by going to your games list in CS2 and click the "Restore Game Backup" button. Those old backup files (ending in .cs2) are not compatible with CS3 and will not be importable in CS3. 

What if things go wrong?

No migration process is perfect, so it's possible things will go wrong during the migration process. If anything out of the ordinary happens, it will be logged in the "Notes" field of your game. For most games that will simply look like this:

If anything went wrong, then it will log those details in the notes field so you can decide if it's something you can fix on your own, or if you want us to try the import a second time.

CS2 > CS3 Migration Notes

For the most part everything will migrate perfectly from CS2 to CS3. For those things that do not migrate perfectly, we have the following notes:

• In CS2 rotation was pretty broken, but it is not in CS3, so any layers that were rotated may not be in the same position in CS3.
• Image layers that were sized by proportional sizing in CS2, likely won’t be laid out correctly. You’ll need to make adjustments to the width, height, object fit, and object position fields in CS3 to get them to lay out correctly.
• Curved text in CS2 text layers worked differently entirely than in CS3. It’s much more powerful and repeatable in CS3, so you’ll need to make adjustments to position and other settings.
• Text sizing (including inline icons), positioning, and wrapping is all way less buggy than it was in CS2. This means that while the text will be very close to what it was in CS2, it may wrap differently, or icons might be sized slightly differently, etc due to bugs fixed in the new text rendering system. 
• The “stroke join” field on boxes no longer exists and is unneeded. It can be accomplished using the corners system.
• All image names must be unique relative to each other and styles.
• CS2 Backup Archives are NOT compatible with CS3.

Changes from CS2 to CS3

There are thousands of changes from CS2 to CS3 as it was a complete rewrite from the ground up; too many things to list here. However, here are some of the more important changes:

Headlining features:

• 100x faster
• Real-time collaboration, even with yourself via multiple-tabs being open
• Nearly perfect migration of designs from CS2
• Free starter design templates 
• Free image library
• Direct access to game-icons.net inside CS3
• Dark mode support

Designer:

• Full anchor and rotation positioning
• Configurable effects pipeline
• Drag and drop organization of layers
• Streamlined user interface for easier discovery of features
• Share a design as a public starter template for you or others to use
• Click on a visual layer and it scrolls to the appropriate layer in the layers panel.
• Fit To button
• Move adjacent button.
• Add Text To buttons
• Add specific image
• Visualization difference between bounds and brim
• Many more corner types
• Corners and borders on images

Datasets:

• Much more robust integration with Google Sheets
• Much more robust CSV imports
• Allow 0 in dataset quantities
• The cite() function can now reference name and quantity in addition to custom columns
• Multi-level enumerations

Other:

• Styles, Game Variables, and Images can be managed outside of a design
• Visual previews in the style list
• Word spacing setting in styles
• Images can be cropped, rotated, and resized right in the image manager.
• You no longer need to mark images as usable in inline icons.
• Added full game cloning.