01
No installation required
The user is working in a supported browser.
2026FileMaker WebDirect. Access your application in a browser.
WebDirect makes selected workflows available through a modern browser. It is useful when users need straightforward access to a FileMaker application.
02
Joint process
Data and rules remain part of the FileMaker solution.
03
Conscious scope
The design takes into account the capabilities, performance and number of WebDirect users.
01Access in browser
FileMaker interface without installing Pro
WebDirect is a client for an application hosted by Server or Cloud. The user logs in in a supported browser and works according to their permissions. FileMaker Pro is still used to create and change applications.
- Shared records with Pro and Go users.
- Login and the scope of data resulting from application permissions.
- Forms, lists and actions tested in the target browser.
- Server or Cloud as application host.
02Compatibility and connection
Compatibility does not mean sameness
Layouts, scripts, file operations, and interface behavior must be tested in the target client. Not every Pro feature works the same in the browser. Large lists, extensive layouts and frequent data refreshes affect the reception of the application.
WebDirect requires host connectivity. It is not an offline solution; testing should take into account delays and session interruptions.
03WebDirect or portal
WebDirect or API-connected portal?
For a controlled group of users of an existing application, WebDirect can limit the scope of a separate front-end. A public portal, unusual interface, or different access model may require a web application with its own permissions layer and API integration.
We make the decision based on tasks, scale, license, required design freedom and responsibility for maintaining both layers.
04Preparing access
From FileMaker layout to working in the browser
We select tasks intended for the web client and check its handling of files, prints, windows and script steps. The test covers keyboard, focus, form readability and permissions. WebDirect accessibility improvements do not replace preparation of the application itself.
Before going live, we determine the number of users, browser compatibility with the host version, network requirements, and how the session ends. A test with a real load helps to select the environment and simplify expensive operations.
Comparison
WebDirect or a separate web application?
| Criterion | WebDirect | Portal connected via API |
|---|---|---|
| Interface | Layouts prepared in FileMaker Pro. | A separate interface designed in web technology. |
| Data and logic | Client for a hosted FileMaker application. | Data exchange through prepared integration. |
| Access | Users and platform licenses require selection. | Own account model; license and API scope still needs to be checked. |
| Maintenance | Application compatibility test with WebDirect and host. | Maintaining the portal, integration and FileMaker environment. |
Questions and answers
Before making a decision
Does WebDirect work offline?
NO. Requires a connection to the host. If the task must run without a network, a different solution and a separate data exchange design are needed.
Will every Pro screen work identically in the browser?
Not every function and script step is handled equally. We test screens, file operations and printouts in target browsers before making them available.
Let’s start with a conversation
Who is to use the application via the WWW?
Describe the tasks, users, and current host. We will check WebDirect and a variant of a separate portal connected to FileMaker.
Discuss browser access