Unsynced patterns can be stored in both theme files and database, making them the most flexible pattern type for development workflows. Theme storage enables version control and advanced features like block-type targeting.
When inserted, unsynced patterns embed their complete block content into the editor. This means the entire pattern becomes part of the template or content where it’s used.
Changes to unsynced patterns don’t sync anywhere – content, styling, and structure modifications remain local to each instance. This provides complete independence after insertion.
This behavior makes unsynced patterns ideal for starting points that need customization per use, rather than components that should maintain consistency across locations.