FileMaker 2026: What’s New and What It Means for Your Business

FileMaker 2026 is here and it marks a shift in how FileMaker solutions get built, maintained, and protected.

Claris is introducing AI-powered, agentic coding directly into the platform. But beyond that, this release is packed with improvements across five distinct themes: AI-ready architecture, developer productivity, disaster recovery, accessibility, and platform stability. If your business relies on FileMaker, this isn’t something to file for later. It’s important to understand now, because it will change how quickly and how effectively you can improve your system.

Let’s walk through what’s changing, what it means day to day, and what look at our own FileMaker systems. Alongside managing hundreds of applications, we also rely on FileMaker to run many of our own mission-critical systems at Fullcity and Codence, so this isn’t hypothetical for us.

What Is “Agentic Coding,” Anyway?

There’s a lot of noise around AI right now, so it’s helpful to ground this in what Claris is delivering.

Agentic coding is essentially an AI assistant that can build within your FileMaker solution alongside your developer. You can describe what you want in plain language, and the AI can generate scripts, layouts, value lists, and more, all within the context of your existing system.

Think of it less like a chatbot, and more like a developer sitting next to you who can move very fast on the mechanical parts of building.

The key point  is that this isn’t a bolt-on tool. Claris is building this directly into the platform with their own engineering teams behind it, which means it will continue to evolve in tandem with FileMaker itself.

Two Sides of the AI Story

One thing we’ve been helping clients understand is that Claris has been investing in AI for a while but in two different ways.

The first is AI working on your data. This is what you’ve already started to see in recent versions things like semantic search, image recognition, and natural language responses. If you’ve used features like Generate Response, you’ve already interacted with this layer.

The second is AI working with your developers. This is the agentic coding side. It’s focused on accelerating how solutions get built and improved. Less time spent on repetitive setup; more time focused on solving the actual business problem.

Both of these are important. But when people talk about agentic coding specifically, they’re talking about that second layer, the development experience. And one distinction to highlight: this is different from “AI in FileMaker” broadly. Agentic coding is specifically about supercharging developer productivity, not about the AI features your users interact with day to day.

What This Means for Your FileMaker Solution

Here’s the part we spend the most time talking about with clients:

AI tools are only as effective as the system they’re working in.

When an AI agent is helping build or modify your FileMaker solution, it’s relying heavily on the structure of what’s already there; your field names, your relationships, your scripts, your overall architecture. That context is what allows it to understand what you’re asking for.

If your system has grown organically over time and most do it may include inconsistent naming, duplicate fields, workarounds that became permanent, or scripts that technically work but aren’t easy to interpret. In that environment, the AI doesn’t have a clean foundation to work from.

That’s where we see the biggest upside.

What Claris is signaling (and what we strongly agree with) is that your system’s architecture is becoming a more direct driver of business value. Clean, well-structured systems will get compounding benefits from these tools. Systems with a lot of technical debt will still improve — but they’ll hit limits faster.

New in FileMaker 2026: Features That Help AI Help You

Several updates in this release that feed directly into how AI interacts with your system and they’re worth knowing about even if you’re not a developer.

Field Annotations let developers define the semantic meaning of a field, separate from its technical name. So instead of only exposing something like cCalc_InvTotal_v2 (the field name) to an AI model, you can also describe it as “Invoice Total” with context about what it represents. That clarity doesn’t just help users it gives AI much better context when generating or interpreting logic. There are also options to customize how fields appear in export dialogs and sort dialogs. If you’re building AI prompts that need to understand your data, this is becomes a key building block.

Table Annotations work the same way at the table level. Developers can now describe what each table represents, and those descriptions are accessible to AI models without any hardcoded strings buried in scripts. It’s your schema describing itself, which is exactly what you want when AI is involved.

Google Gemini Support rounds out FileMaker’s growing list of supported AI providers, which now includes OpenAI, Anthropic, Cohere, and Google. If your organization already works within the Google Cloud ecosystem, this removes a friction point and gives your team more flexibility in how AI gets used within your FileMaker solution.

If you’re planning an upgrade, these are features we’d suggest thinking about more strategically not just enabling them but using them intentionally to improve how your system communicates context.

Your Data, Safer Than Ever

One theme in this release that doesn’t always get the attention it deserves is disaster recovery and FileMaker 2026 makes substantial improvements here.

Remote Backup is now built into FileMaker Server. Backups upload automatically to cloud storage on a 20-minute schedule, managed centrally across all your servers from the Claris Customer Console. When you need to restore, the system validates integrity before applying the restore not just copying files. For organizations with compliance requirements around data protection (HIPAA, SOC 2, ISO 27001), this is a major improvement.

Standby Server makes high-availability deployments much more accessible. A synchronized second server stays continuously updated, so when something goes wrong, planned maintenance or an unexpected outage, failover takes minutes, not hours. If your business can’t afford extended FileMaker downtime, this is worth taking a serious look at.

Auto-Restart After Crash is exactly what it sounds like. If the Web Publishing Engine, OData service, or Data API encounters an issue and crashes, it now restarts itself automatically. Recovery time drops from “however long until someone notices” to seconds. For organizations relying on WebDirect or API integrations for day-to-day operations, this is a quiet but important reliability upgrade.

A Better Experience for Your Users

FileMaker 2026 also makes real progress on accessibility, and this is a bigger deal than you might think.

WebDirect, the browser-based way to access FileMaker solutions, now includes significant accessibility improvements: updated semantic HTML, proper ARIA attributes on fields and buttons, improved keyboard navigation, and dynamic content changes that are detectable by screen readers. This is a big step toward WCAG 2.1 compliance.

The notable thing here is that your existing layouts benefit automatically, no redesign required. For organizations in government, healthcare, education, or any environment with accessibility requirements under ADA or Section 508, this opens doors that may have previously been closed.

The Developer Experience Gets a Real Upgrade Too

We want to be transparent about why developer experience improvements matter to you as an organization because faster, cleaner development means lower cost and better outcomes on your projects.

A few highlights from this release:

Control Field Entry by Calculation is a feature that replaces a common workaround in FileMaker. Developers can now control whether a field is editable based on any logic they define (user role, record status, workflow stage). This means smarter, safer user interfaces without the scripting complexity that used to require to achieve this.

PDF handling is now native in FileMaker scripting. Developers can build, assemble, and save multi-page PDFs entirely within Script Workspace, no plug-in required. For organizations that generate reports, document packets, or automated exports, this simplifies workflows and eliminates a dependency.

Enhanced Inspector on macOS reduces the layout design interface from four tabs to two, surfacing only what’s relevant to what’s selected. Less friction for developers means fewer hours billed to routine layout work.

There’s also a long list of smaller quality-of-life improvements throughout the release — things that each individually save a few minutes here and there but collectively add up to a noticeably smoother development experience.

Platform Keeping Pace With Modern IT

On the infrastructure side, FileMaker 2026 has been certified for macOS Tahoe 26, Windows Server 2025, and ships with updated security libraries — OpenSSL 3.5 LTS (supported through April 2030) and Apache Tomcat 10.1.44+, which addresses a known security vulnerability for any internet-facing deployment. IPv6 support has also been added for environments running dual-stack networks.

These updates may not be exciting on the surface, but they matter. They mean your FileMaker environment stays compatible with modern operating systems and your IT team’s security requirements don’t bump up against an outdated platform.

What’s Coming and When

Claris is releasing the agentic coding plugin as a developer preview this summer so developers can start using it and provide feedback early. From a planning perspective, here’s where we’d start:

Understand what FileMaker 2026 means for your roadmap. Features like field annotations, table documentation, broader AI provider support, and infrastructure upgrades lay the groundwork for future AI capabilities. It’s worth discussing timing and upgrade paths for your environment.

Assess the health of your system. This is often where the biggest opportunity lies. If your system has extra fields, legacy structures, or unclear naming, now is a good time to address it—not just to clean up, but to prepare for what’s next.

Set the right expectations. Agentic coding is powerful, but it doesn’t replace strategy or expertise. The most value will come from pairing these tools with a clear roadmap and a well-structured system.

This is exactly the kind of conversation we’ve been having with clients, looking at where things stand today and where it makes sense to invest next.

If you want to go deeper on the technical side of AI-assisted FileMaker development, our FileMaker AI Foundations series is a good place to start. It covers how FMXML and the FM Clipboard Tool fit into this workflow and how FM AI Paste works in practice.

The Bigger Picture

Stepping back, this is part of a longer evolution for the FileMaker platform.

We saw it with FileMaker Go, then cloud deployments, and now AI-assisted development.

Each step has made the platform faster, more accessible, and better aligned with how modern businesses operate.

FileMaker 2026 isn’t just one new feature. It advances reliability, accessibility, developer experience, and AI-readiness all at once—and that breadth is what makes it worth watching.

We’re excited about where this is going and what it will enable for the organizations we work with.

If you’re thinking about FileMaker 2026 and what it means for your system or want a gut check on your readiness for AI-driven development, we’re always happy to connect. Request a consultation here.