Delphi 13 Community Edition: free tier jumps three versions at once

Development
, , , ,
1

Delphi 13 Community Edition: the free tier jumps three versions at once — what you get and what stays out

By Devy · Category: Desarrollo / Development

On August 11, Embarcadero released Delphi 13 Community Edition, and Marco Cantu’s announcement opens with the usual dryness: “Embarcadero is pleased to announce the availability of Delphi 13 Community Edition, the latest free edition of our professional Delphi development environment.”

That dryness hides the real news. The free tier was stuck on 12.1. Now it moves to 13 Florence, which means everything that shipped in 12.2, 12.3, and 13.0 arrives in a single install. If you were using CE, you didn’t miss one release: you missed three. This is the “what happened while I wasn’t looking” note.

And it matters where this lands. The installed base of Delphi in Latin America is large and concrete: management software, point-of-sale systems, vertical business applications that have been shipping and receiving maintenance for two decades. A free tier that advances three versions isn’t an abstraction for those teams — it’s whether the person maintaining the app can open it in a current IDE without a purchase order.

The language changes

Four deserve your attention by name, because they change how you read everyday code.

The ternary operator, written with if. Delphi finally has an inline conditional expression. Where you used to write an if/else block or reach for IfThen from System.Math (which evaluates both branches, a footgun that’s bitten all of us at least once), now you have a proper expression form using the if keyword.

NameOf. An intrinsic that returns the name of an identifier as it appears in the source code, as a string. Logging, property-change notifications, and anything that historically was a hardcoded string next to a symbol: those strings now survive a rename.

is not and not in. Negated forms of two operators that used to require parentheses and a not upfront, which is one of those things that read well when you write them and badly when you read them six months later.

The compiler directives {$PUSHOPT} and {$POPOPT}. They save and restore compiler option state, so a block that needs a specific configuration can return things to how they were instead of leaving your unit in whatever state the last directive set. Along with that: a noreturn directive for procedures that don’t return, and expanded constraints for generic types.

None is dramatic on its own. Together they’re what three versions of language work looks like when it lands all at once.

The 64-bit IDE

This is the item most likely to change your day.

Delphi 13 brings a native 64-bit IDE with a 64-bit Delphi language server, and CE includes both the updated 32-bit IDE and the new 64-bit one. The language server is what matters: DelphiLSP running as a 32-bit process has been the ceiling for large projects for years — code completion degrading, the IDE slowing down, memory pressure on codebases that are large but nothing out of the ordinary. A 64-bit LSP raises that ceiling.

Also in the IDE: a Focus Mode for distraction-free editing, search and filtering within IDE panels, and split editor views.

Mobile: where version numbers get specific

For Android, Delphi 13 compiles native ARM apps in 32 and 64 bits with an updated toolchain, targets API level 35, and supports Android 15 features including 16 KB memory pages — the alignment requirement that’s been silently breaking native libraries across the Android ecosystem. If you ship an Android app made in Delphi, this is the release that gets you compliant.

For Apple platforms, they’re native iOS apps for iOS 18, both on physical devices and on the iOS Simulator on Macs with Apple Silicon. That last part deserves its own sentence: simulator support on Apple Silicon means you can develop and test on the Mac you actually have, instead of keeping an Intel machine alive for that.

The license, in clear terms

This is the part to read before planning around it, because the restrictions are real and not all obvious.

  • One year, counted from your first download or unsealing. It does not auto-renew.
  • To continue after expiration, you reinstall the latest Community Edition and accept the terms again. That’s the documented path, not a workaround.
  • Less than US$5,000 in annual revenue — for both freelancers and startups. If you cross that, a paid license is required.
  • Up to five developers. Above that, Professional or higher.
  • No Kai — the AI assistant is sold separately and only for paid editions.
  • No update subscription, no technical support, no access to previous versions, no network licenses.
  • Local and embedded database connectivity only. Access to remote databases is Enterprise/Architect.
  • CE cannot be installed alongside a paid edition of the same version, and installs only through the GetIt web installer — not with InstallAware’s offline installer.

The one-year term without auto-renewal is the point most misunderstood. It’s not a trial that stops working, and it’s not perpetual either: it’s annual re-consent, and that re-consent is tied to reinstalling whichever CE is current at that time.

The gap nobody put in the headline

Here’s what the announcement doesn’t frame: Community Edition is based on 13.0, and the paid product is already at 13.1.

RAD Studio 13.1 Florence Update 1 shipped on March 19, 2026 — five months before this CE release. It added the native Delphi compiler targeting Arm64EC for Windows on Arm, Android API level 36, iOS 26, a standalone FireMonkey Style Designer, Windows 11 VCL styles, integrated bookmarks, LSIF indexing for DelphiLSP, and updated database drivers.

None of that is in Community Edition. The practical version of the difference is API levels: CE targets Android API 35 and iOS 18; the paid tier targets API 36 and iOS 26. For a hobby project that difference is nothing. For an app you actually publish in a store, the target API level is a compliance deadline, not a preference — and it’s the specific reason a CE user hits a wall that has nothing to do with the language or the IDE.

So the honest framing of this release: the free tier caught up with three versions of language and IDE work, and at the same time stays one release behind on platform targets. Both things are true.

Who should install it today

If you maintain a Delphi codebase and were on 12.1 or earlier, an afternoon is worth it — especially for the 64-bit language server, which is the difference between an IDE that handles your project and one that doesn’t. If you’ve never written Pascal and you keep running into Delphi code in the real world, a free and complete IDE with visual designers and a real debugger is a reasonable way to find out what this is all about.

If you publish to app stores, check your target API level against 35 before planning anything. That’s the number that decides whether CE is a tool or a temporary patch for you.

Download: Download the Free Delphi Community Edition - Embarcadero

And you? If you maintain Delphi in production, what holds you back more today — the IDE version, or the mobile toolchain version?

Sources: