FileMaker 2026 - what's new, and should you upgrade?

Every FileMaker release gets the same two reactions: the people who've been asking for one specific feature for years, and everyone else wondering whether it's worth the upgrade window. FileMaker 2026 (released June 2026) is a release we'd put firmly in the "worth planning for" camp - not because it reinvents the platform, but because it quietly fixes three things that have cost FileMaker teams real money: fragile disaster recovery, AI that didn't understand your data, and a hundred small friction points in day-to-day development.

Here's our breakdown of what's in the release, what it means in practice, and who should move first. As a working UK Claris Partner, our bias is towards the things that change outcomes for a business - not the demo-friendly features.

The headline: real disaster recovery, built in

For years, "disaster recovery for FileMaker" meant a nightly backup and a hope. FileMaker Server 2026 introduces two optional add-on services that finally give the platform a proper business-continuity story:

• Remote Backup - automated, encrypted offsite backups of your FileMaker data to secure, Apple-managed cloud infrastructure, every 20 minutes, with no manual effort. A genuine offsite copy, not another file on the same box.
• Standby Server - a secondary server kept in continuous sync with your primary. If the primary fails, you switch over in minutes instead of restoring from backup over hours.

Used together, these give you a recovery-point objective measured in minutes and a recovery-time objective measured in minutes too. That is a step change for any organisation that runs its operations on FileMaker. They're paid add-ons on top of FileMaker Server, and for most of our clients they're the single clearest reason to move to 2026. If you've never actually tested a restore, this is the nudge to fix that - see our FileMaker Security & UK GDPR checklist for the backup and recovery posture we look for on every audit.

AI that actually understands your data

FileMaker has shipped native AI tooling since 2024, but the models often didn't understand the database they were pointed at - a field called t_c_01 means nothing to an LLM. FileMaker 2026 addresses this directly:

• Field and table annotations - the Database Manager now has dedicated settings (via an "Advanced" panel) to describe what a field actually means. That description is included in the DDL the AI models read, so natural-language queries and semantic search get meaningfully more accurate. No more abusing the field comment with an [LLM] prefix.
• Custom field display names - friendlier names that flow through to native operations like sorting and exporting, making the system more intuitive for end users too.
• New functions - FieldAnnotation(), BaseTableComment() and FieldDisplayNames() let you read this metadata programmatically.
• Google Gemini support - added alongside the existing LLM providers, giving you more choice in how you wire AI into your solution. Your data stays under your control as a FileMaker standard.

This is unglamorous but important plumbing. If you've been waiting to add AI features and found the results unreliable, better schema context is often the missing piece. For what genuinely works in production today, read AI & LLMs inside FileMaker - what actually works in 2026.

Less friction, more building

This is the part developers will feel every day. Claris collected a long list of quality-of-life requests and shipped them:

• The Smart Inspector - the Layout Inspector has been reworked from four tabs down to two, and now adaptively shows only the options relevant to the object you've selected. Far less scrolling past settings that don't apply.
• Conditionally editable fields - you can now make a field editable based on a Boolean expression, instead of stacking two fields with opposite hide conditions or maintaining duplicate layouts. This alone removes a mountain of fiddly layout work.
• A new suite of PDF script steps - Create PDF, Open PDF, Append PDF, Close PDF and Print PDF. Together they let you build, merge and output PDFs in memory without the old workarounds.
• Save as XML, overhauled - a new dialog lets you choose which catalogs to export (accounts, base tables, layouts, scripts and more) and export binary layout data separately. This is what unlocks real version control and CI/CD workflows for FileMaker solutions.
• Script Workspace improvements - commented/disabled code can now be collapsed, and custom functions can live in folders with an option to restrict editing to Full Access or all users.
• Smaller wins - Show Custom Dialog now supports custom size and position; Configure Persistent Data and Get(PersistentData) for reading and writing persistent storage; cached JSON from Insert from URL; flash control on Insert from Device; a customisable zoom level; and more.

Infrastructure that holds up

Beyond the headline add-ons, the server itself is more self-healing. Services like the Web Publishing Engine now recover automatically from crashes, so your deployment demands less babysitting. FileMaker 2026 also adds full compatibility with macOS 26 and Windows Server 2025, keeping you supported and compliant, and WebDirect makes real progress toward WCAG 2.1 and Section 508 accessibility - existing layouts benefit automatically, with no redesign required.

What's coming next

Claris has been clear that 2026 lays groundwork rather than finishing the story. Developer previews of agentic development capabilities are expected later in the summer - the aim being to make FileMaker a first-class target for the AI coding tools developers already use. We'd treat that as a reason to get on a current version now, so you're ready when those previews land, rather than a reason to wait. For where we think the platform is heading, see The Future of FileMaker.

Our verdict: should you upgrade?

Short version: yes for most, but plan it properly. Here's how we'd advise by situation:

• You run FileMaker Server and DR keeps you up at night - upgrade, and budget for Remote Backup and Standby Server. This is the strongest case in the release.
• You have an active development team - upgrade. The Smart Inspector, conditionally editable fields, PDF steps and XML-for-version-control will pay back in developer time within weeks.
• You're planning AI features - upgrade to get annotations and Gemini support as your baseline before you build.
• You're on FileMaker 19 or older perpetual licences - this is a good moment to move to the current subscription and right-size your user count. Get independent advice on the licensing first.
• You're mid-project on a tight deadline - wait until your next maintenance window. Don't change platform versions the week before go-live.

As with any upgrade, the risk isn't the new version - it's the plugins, integrations and custom hosting around it. Test in a staging copy, check plugin compatibility, and confirm your backups restore before you cut over. If you'd rather not do that alone, that's exactly what our FileMaker support and Health Check services are for. Moving off a legacy deployment at the same time? Our migration runbook walks through it step by step.

The short answer

FileMaker 2026 is a resilience-and-refinement release that makes the platform more dependable and pleasant to build on, while quietly preparing it for an AI-first future. The disaster-recovery add-ons are the standout - genuinely new capability, not a tweak - and the developer quality-of-life changes will be felt on day one. For most organisations the question isn't whether to upgrade, but when. Plan the window, test the edges, and you'll be on a stronger footing than you were.

See also - Is FileMaker still worth using in 2026?, AI & LLMs inside FileMaker, and FileMaker Security & UK GDPR.