The Claris FileMaker Developer Tool is a command-line utility for performing administrative, diagnostic, security, and deployment operations on FileMaker database files.
Its command name is FMDeveloperTool, and it is included with current versions of FileMaker Server for Windows, macOS, and Linux.
The Developer Tool provides many of the capabilities traditionally available through the Developer Utilities in FileMaker Pro, but it can run directly on a server and be integrated into automated workflows.
What Can the FileMaker Developer Tool Do?
The Developer Tool can perform several types of operation on .fmp12 files, including:
- creating a copy or clone;
- creating a compressed or self-contained copy;
- renaming files and updating internal file references;
- saving a FileMaker app as XML;
- encrypting or decrypting files;
- removing administrator access;
- enabling Kiosk mode;
- checking file consistency;
- recovering a damaged file;
- measuring the space used by tables, fields, and indexes;
- uploading databases to FileMaker Server;
- regenerating a database’s unique identifier;
- changing the password of a FileMaker file account.
These features make it useful to FileMaker developers, server administrators, hosting providers, and teams maintaining automated deployment processes.
A Command-Line Version of Developer Utilities
Several Developer Tool operations are also available through the graphical Developer Utilities in FileMaker Pro.
The important difference is where and how they can be performed.
With FileMaker Pro, an administrator may need to download a database from the server, open the appropriate desktop tools, perform the operation, and upload the resulting file again.
The Developer Tool can run directly on the server. This avoids unnecessary file transfers and makes it possible to automate repeatable operations with system scripts.
It is particularly useful when working with large databases or externally stored container data, where downloading and uploading the complete application may take considerable time.
Creating Copies and Clones
The Developer Tool can create several types of FileMaker file copies.
A standard copy contains the application structure and all its records. A clone contains the complete structure, including tables, fields, layouts, scripts, and relationships, but no record data.
Clones are particularly important when using the FileMaker Data Migration Tool, which transfers production data into the updated structure of a new application version.
The Developer Tool can also create compressed copies and self-contained files. A self-contained copy brings externally stored container data back into the FileMaker database file, making the application easier to move or archive as a single unit.
Renaming Multi-File Applications
Renaming a FileMaker file is not always as simple as changing its filename.
A complex custom app may contain several related files with internal references to one another. Renaming one file manually can break those references.
The FileMaker Developer Tool can rename one or several files while updating compatible internal database-source links. It also supports pattern-based renaming, which is useful when preparing different versions or deployments of a multi-file application.
This makes renaming safer and more practical than modifying each reference manually.
File Encryption and Security
The Developer Tool can encrypt or decrypt FileMaker files using FileMaker Encryption at Rest.
Encryption protects a database if someone obtains physical access to the file or its backup. Without the encryption password, the file’s contents cannot simply be opened and examined.
The tool can also remove administrator access permanently from a distributed copy of an application. This may be useful for commercial FileMaker products whose developer does not want customers to access or modify the underlying structure.
Because these operations affect access to the file, they must be carefully planned. Passwords and encryption keys should be stored securely, and the original file should always be preserved in a protected location.
Consistency Checks and Recovery
The FileMaker Developer Tool can check the internal consistency of a database and attempt to recover a damaged file.
A consistency check can help detect structural problems without opening the file in FileMaker Pro. Recovery attempts to rebuild a file sufficiently to retrieve its data.
However, a recovered file should not normally be returned directly to production. Recovery is an emergency process, not a repair strategy. The recommended objective is to extract the data and transfer it into a known-good clone or backup.
Reliable FileMaker hosting therefore depends primarily on frequent verified backups. Recovery tools are a last resort when no healthy copy is available.
Understanding File Size
A FileMaker file may grow unexpectedly because of record data, embedded containers, or large field indexes.
The Developer Tool can report the space used by a table or field and list the fields or indexes consuming the most storage.
This can help developers identify:
- unexpectedly large container fields;
- text fields containing excessive data;
- indexes consuming significant disk space;
- tables responsible for most of the database’s growth.
These diagnostics are useful when optimizing storage, investigating performance, or preparing a large application for migration.
Saving a FileMaker App as XML
The Developer Tool can produce an XML representation of a FileMaker custom app.
This XML can describe elements such as tables, fields, relationships, scripts, layouts, themes, value lists, custom functions, accounts, and privilege sets. Developers can export the complete application structure or select particular categories.
Because XML is a text format, it can be inspected with external tools, compared between versions, stored in version-control systems, and used in automated development workflows.
The XML does not replace the original FileMaker file, but it provides a machine-readable representation of its structure.
Uploading Databases
The Developer Tool can also upload databases to a FileMaker Server host.
It can upload one file, several files, or the contents of a folder. Depending on the selected options, it can include or exclude externally stored container data and automatically open the databases after upload.
Before uploading, the tool performs security and consistency checks similar to those performed by FileMaker Pro.
This capability helps automate deployment workflows without requiring a developer to upload every file manually through FileMaker Pro.
Developer Tool vs. Data Migration Tool
The FileMaker Developer Tool and the FileMaker Data Migration Tool serve different purposes.
The Developer Tool performs operations on the FileMaker file itself, such as copying, cloning, encrypting, renaming, checking, recovering, analysing, or uploading it.
The Data Migration Tool transfers records and user accounts from an existing production file into a clone containing a newer application structure.
The two tools complement each other. For example, the Developer Tool can create a clone, and the Data Migration Tool can then populate that clone with current production data.
Automation and Professional Deployment
Because the FileMaker Developer Tool operates from the command line, its operations can be included in system scripts, deployment pipelines, and scheduled administrative processes.
A workflow might:
- preserve a protected copy of the original database;
- perform a consistency check;
- create a clone or XML representation;
- encrypt the resulting file;
- migrate production data;
- upload the new version to FileMaker Server;
- record the result in a deployment log.
Automation makes the process repeatable, but it must still include verification, secure credential management, error handling, backups, and a rollback plan.
The FileMaker Developer Tool and fmcloud.fm
fmcloud.fm operates FileMaker Server infrastructure on Linux and Windows and has extensive experience with FileMaker deployment, security, migration, and recovery tools.
Running these utilities correctly requires more than knowing the command syntax. The database must be safely closed, protected by a current backup, handled with the correct credentials and encryption keys, and verified before being returned to production.
Our team can assist customers and developers with operations involving clones, encryption, XML exports, file diagnostics, migration, recovery, and deployment while the underlying server environment remains securely managed by fmcloud.fm.
Conclusion
The FileMaker Developer Tool brings important file-management and developer operations to the command line.
It can create copies and clones, rename and encrypt files, export application structures as XML, perform consistency checks, analyse storage, recover damaged databases, and upload applications to FileMaker Server.
Its main benefits include:
- performing operations directly on the server;
- avoiding unnecessary transfers of large databases;
- automating repeatable administrative tasks;
- supporting professional deployment workflows;
- improving diagnostics and storage analysis;
- integrating FileMaker files into version-control and CI/CD processes.
Together with the Data Migration Tool, the Developer Tool provides the foundation for safer, more automated, and more professional FileMaker application deployment.
