Overview
Learn about the different methods for deploying WebViewer code to your FileMaker file.
The FileMaker Web Viewer object is a powerful way to build rich, interactive experiences for your FileMaker users. In many ways, it's simpler than a traditional browser-based web app because you can host the code inside of your FileMaker file (rather than hosting on a web server) and you don't have to deal with authentication because you can rely on the FileMaker Pro client.
FAQ
What is the difference between the WebViewer and the browser-based project created with the ProofKit CLI?
The primary difference is the framework and runtime shape. Browser-based projects use Next.js while the WebViewer starter uses Vite with a small browser-only React app. That keeps the WebViewer scaffold close to a stock Vite starter while still being ready for ProofKit WebViewer integration, Tailwind v4, and shadcn component installs.
Can I build WebViewer applications using Next.js?
Yes! This is sometimes preferred if you already hae a web app and want to keep things in a single codebase, or if you're already hosting the web app and don't need the FileMaker app to work offline. Simply point your webviewer object to the URL of your existing web app or local dev server and use the @proofkit/webviewer package to interact with FileMaker scripts and data.
Does this technique work in Web Direct?
Yes. The ProofKit WebViewer Addon includes a custom function that wraps your web code so the injected FileMaker JavaScript code will still interface with the WebViewer, even in Web Direct.
Do I need a hosted FileMaker server to start?
No. You can scaffold the WebViewer app without hosted FileMaker credentials. When you are ready to generate layout clients, ProofKit prefers the local FM MCP path first and only needs hosted server setup if you choose that route.