--- title: Xcode 27.2 introduces a JSON-based project format to... description: Xcode 27.2 introduces project.xcproj, a new JSON-based project file format designed to replace the long-standing project.pbxproj format found in .xcodeproj... canonical: https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Xcode 27.2 introduces a JSON-based project format to replace pbxproj | daily.dev og:description: Xcode 27.2 introduces project.xcproj, a new JSON-based project file format designed to replace the long-standing project.pbxproj format found in .xcodeproj... og:url: https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf og:image: https://api.daily.dev/og/posts/oQVV96eQF.png og:image:alt: Xcode 27.2 introduces a JSON-based project format to replace pbxproj og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Xcode 27.2 introduces a JSON-based project format to replace pbxproj **[Collections](https://daily.dev/sources/collections)** · 3 min read · 5 upvotes · 0 comments ## Summary Xcode 27.2 introduces project.xcproj, a new JSON-based project file format designed to replace the long-standing project.pbxproj format found in .xcodeproj bundles. The new format restructures the build graph as a readable tree using names and paths instead of opaque UUIDs, and reverses file-to-target membership so files declare their own targets. Apple frames this as improving mergeability and making projects easier for coding agents to parse. Existing projects are not auto-converted; both formats are supported side by side, and tools like Tuist, XcodeGen, Bazel, and SwiftPM continue working unchanged. Apple also released an open-source spec and a validator/reformatter tool called xcprojformatter. The feature currently ships as part of a beta release. ## Content Xcode 27.2 ships with a long-overdue change to how projects are stored on disk: a new JSON-based `project.xcproj` file that replaces the decades-old `project.pbxproj` property list format. ## What's wrong with pbxproj If you've ever had to resolve a merge conflict in a `.pbxproj` file, you know the pain. The format is a flat object graph where everything is keyed by opaque hex IDs, build settings are duplicated across per-configuration blocks, and relationships between files and targets are hard to follow without Xcode open in front of you. ## What the new format does differently The new `project.xcproj` format restructures all of this: - **Tree structure instead of flat graph.** The layout mirrors what you see in Xcode's UI, so the file is actually readable. - **Names and paths instead of hex IDs.** Cross-references use human-readable identifiers. IDs are only assigned where genuinely necessary, like targets and build products. - **Files declare their own target membership.** The relationship direction is reversed, which reduces the kind of conflicting edits that make merges painful. - **Collapsed build settings.** Instead of duplicated blocks per configuration, settings live in a single block with inline conditions. Apple also explicitly frames this as making Xcode projects easier for coding agents to work with, which tracks given the structural improvements. ## How to adopt it New projects in Xcode 27.2 default to the JSON format. Existing projects aren't auto-converted - you can switch via the File inspector's Project Format picker. Both Xcode 27.0 and 27.2 can open JSON-format projects, so the format itself isn't a hard compatibility break. Apple also released an open-source [xcode-project-format spec](https://github.com/apple/xcode-project-format) and an `xcprojformatter` tool for validating and reformatting project files. ## What to watch out for The catch is third-party tooling. CocoaPods, XcodeGen, Tuist, CI scripts, and anything else that parses `project.pbxproj` directly will need updates before they can handle the new format. Tuist, XcodeGen, Bazel, SwiftPM, and xcconfig workflows continue working as before in the meantime - they just won't benefit from the new format until they adopt it. If your team is fully on Xcode 27 with no external tooling dependencies on pbxproj, switching now makes sense. If you have mixed Xcode versions or rely on tools that haven't updated yet, it's worth waiting. It's worth noting that Synchronized Folders (introduced in Xcode 16) already addressed file-list merge conflicts. The JSON format goes further by also fixing the duplicated build settings problem, so the two changes together cover most of the common pbxproj pain points. ## Questions this post answers ### What is the new project.xcproj format in Xcode 27.2 and how does it differ from pbxproj? Xcode 27.2 introduces project.xcproj, a JSON-based project format that replaces the old flat, UUID-heavy project.pbxproj format. It structures the build graph as a tree mirroring the Xcode UI, uses names and paths instead of opaque IDs for cross-references, and reverses file-to-target membership so files declare their own targets rather than targets listing files. This produces cleaner diffs and fewer merge conflicts. _Teams tracking Xcode project tooling changes can follow format shifts like this one on daily.dev._ ### Do I need to convert my existing Xcode project to the new xcproj format? No, existing projects are not automatically converted to the new xcproj format in Xcode 27.2. Both pbxproj and xcproj are supported side by side, with new projects defaulting to xcproj. Tools like Tuist, XcodeGen, Bazel, SwiftPM, and xcconfig-based workflows continue working unchanged and can adopt the new format at their own pace. _Developers weighing when to migrate build tooling can track compatibility notes like these on daily.dev._ ### Why did Apple replace the pbxproj format in Xcode with a JSON-based format? Apple redesigned the project file format primarily to reduce merge conflicts and make diffs easier to read, since pbxproj's flat, ID-heavy structure was notoriously hard to merge. Apple also explicitly states the new xcproj format makes it easier for coding agents to interact with Xcode projects, which is widely seen as a major driver behind the change. _Developers navigating AI-agent-friendly tooling shifts can follow updates like this on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 3 discussions and 97 comments across x (as of 2026-09-17). **TL;DR:** Reaction to the JSON-based project format is largely enthusiastic and relieved after years of painful pbxproj merge conflicts, though some push back that JSON still needs canonicalization and tooling support to truly fix things, and a few would have preferred alternatives like Pkl or Tuist-style DSLs. **Sentiment:** 68% positive · 24% mixed · 8% skeptical **The case for** - Many say pbxproj/xcproj merge conflicts were a long-standing pain point that this finally addresses. - JSON is seen as far easier to read, parse, and reason about than the old property-list format. - Some note this should help third-party tooling, linting, and AI coding agents parse projects more reliably. **The pushback** - One commenter argues the format only reduces merge conflicts if Xcode keeps object ordering and identifiers stable. - Another warns this just moves 'pbxproj archaeology' into JSON unless the JSON is canonical and CI can rebuild/diff it. - Some feel a DSL-based approach like Tuist would still be more convenient than raw JSON merges. - A few would have preferred formats like Pkl or YAML instead of JSON. - There's confusion/skepticism about the odd version numbering (27.2 before 27.1) unrelated to the format itself. **By community** - x (positive): Overwhelmingly positive and even giddy reactions to killing off pbxproj, with a handful of pragmatic concerns about canonicalization, ordering stability, and whether JSON was the best choice versus alternatives. **Hottest debate:** Whether JSON actually solves merge conflicts by design, or only helps if Xcode keeps output stable and canonical enough for real diffing. **Open questions** - Does editing a field via the GUI cause the entire JSON file to be regenerated and reordered? - Will Xcode keep object ordering and identifiers stable enough for JSON diffs to actually reduce merge conflicts? - Will third-party tools and CI pipelines that rely on canonical rebuild-and-diff checks be able to trust the new format? **Highlights** > @twostraws json only helps merge conflicts if xcode keeps object ordering and identifiers stable > — [sebuzdugan on x](https://x.com/sebuzdugan/status/2100557825969700866) > @twostraws That could make project-file changes reviewable at last—if the JSON is canonical rather than a generated export. The release gate I’d want: rebuild the project from a clean checkout in CI, then diff the result. Otherwise we just moved .pbxproj archaeology into JSON. > — [onlyapps\_org on x · 4 points](https://x.com/onlyapps_org/status/2100284541466267948) > @twostraws It’s cool but nowhere as convenient as a DSL based project definition with something like Tuist. Project merges will still be painful. > — [bvirlet on x](https://x.com/bvirlet/status/2100351818786103689) > @twostraws xcproj files caused more merge conflicts than the actual code. good riddance. > — [irastech on x](https://x.com/irastech/status/2100359627581894962) > @__JoshuaJRoot__ @twostraws except plists don't need parsing and can be loaded directly into memory, and can also be trivially transformed to/from json if needed for readability > — [lensovet on x · 1 points](https://x.com/lensovet/status/2100301451281019172) **Source threads** - [x](https://x.com/seanallen_dev/status/2100289039932793186) · 0 points · 0 comments - [x](https://x.com/twostraws/status/2100283081399668898) · 0 points · 85 comments - [x](https://x.com/twostraws/status/2100281950246154364) · 0 points · 12 comments --- Tags: [#apple](https://daily.dev/tags/apple), [#ios](https://daily.dev/tags/ios), [#xcode](https://daily.dev/tags/xcode) [View this post on daily.dev](https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Xcode 27.2 introduces a JSON-based project format to replace pbxproj","url":"https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf"},"datePublished":"2026-09-17T06:30:28.957Z","dateModified":"2026-09-17T19:28:16.341Z","description":"Xcode 27.2 introduces project.xcproj, a new JSON-based project file format designed to replace the long-standing project.pbxproj format found in .xcodeproj...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9d4b0f7ce8bd48f4221837e3ae3a9f8e?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9d4b0f7ce8bd48f4221837e3ae3a9f8e?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"apple,ios,xcode","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Xcode 27.2 introduces a JSON-based project format to replace pbxproj"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/xcode-27-2-introduces-a-json-based-project-format-to-replace-pbxproj-oqvv96eqf#faq","mainEntity":[{"@type":"Question","name":"What is the new project.xcproj format in Xcode 27.2 and how does it differ from pbxproj?","acceptedAnswer":{"@type":"Answer","text":"Xcode 27.2 introduces project.xcproj, a JSON-based project format that replaces the old flat, UUID-heavy project.pbxproj format. It structures the build graph as a tree mirroring the Xcode UI, uses names and paths instead of opaque IDs for cross-references, and reverses file-to-target membership so files declare their own targets rather than targets listing files. This produces cleaner diffs and fewer merge conflicts. Teams tracking Xcode project tooling changes can follow format shifts like this one on daily.dev."}},{"@type":"Question","name":"Do I need to convert my existing Xcode project to the new xcproj format?","acceptedAnswer":{"@type":"Answer","text":"No, existing projects are not automatically converted to the new xcproj format in Xcode 27.2. Both pbxproj and xcproj are supported side by side, with new projects defaulting to xcproj. Tools like Tuist, XcodeGen, Bazel, SwiftPM, and xcconfig-based workflows continue working unchanged and can adopt the new format at their own pace. Developers weighing when to migrate build tooling can track compatibility notes like these on daily.dev."}},{"@type":"Question","name":"Why did Apple replace the pbxproj format in Xcode with a JSON-based format?","acceptedAnswer":{"@type":"Answer","text":"Apple redesigned the project file format primarily to reduce merge conflicts and make diffs easier to read, since pbxproj's flat, ID-heavy structure was notoriously hard to merge. Apple also explicitly states the new xcproj format makes it easier for coding agents to interact with Xcode projects, which is widely seen as a major driver behind the change. Developers navigating AI-agent-friendly tooling shifts can follow updates like this on daily.dev."}}]} ```