You can add a full rich text editor to FileMaker with a web viewer, and you only need to build it once. Kyo Logic’s free Rich Text Editor add-on runs the Summernote editor inside a web viewer, lets you set up as many separate configurations as you need, and writes changes back to the connected FileMaker field as the user types.

Here is the moment it exists for. Your team writes the scope section of every quote in FileMaker. Someone needs a bulleted list, a bold warning, and a link to the spec sheet. They write it in Word, paste it in, and the formatting falls apart. Next week a different screen needs a stripped-down notes editor, and a developer starts building a second editor from scratch.

Why does rich text get complicated in FileMaker?

FileMaker text fields support basic character styling from the Format menu, but users now expect a toolbar: lists, headings, links, and the buttons they know from every web app. Embedding one editor in a web viewer is a reasonable afternoon of work.

The hard part is the second and third editor. One screen needs three buttons. Another needs the full set for templates and documentation. Each new editor usually means new scripts and new plumbing between the web viewer and the field. That is the part this add-on was built to remove.

What the add-on does out of the box

• Built on Summernote. Summernote is a well-documented open source editor, so its options and behaviors are clearly defined, and it is simple enough that configuration changes stay easy.
• Many configurations, one component. Create as many standalone configurations as you need, each pointing to a different field. Keep one minimal and give another the full toolbar.
• The FileMaker communication is already handled. The link between the editor and FileMaker is abstracted out, so adding a configuration does not mean writing new scripts or field-level plumbing.
• Background saves. The editor updates the connected field as the user types.

Why a repeatable pattern beats a one-off editor

The value is not rich text on one screen. It is having a pattern you can reuse every time a new use case appears, without starting over. A quote template, a product description, a client update, and an internal procedure can each get the editor they need from the same component.

Because Summernote has a fairly extensive API, there is room to go further when a solution needs more than the default setup. And if you are already improving the screens your team writes on, the Multi-File Uploader handles the attachments that usually sit next to that text, and the Audit Log & Version History add-on records who changed it.

What this could look like in your solution

Start with the field people complain about most. Usually that is the one where formatted text matters to a customer: quote scopes, job instructions, or report narratives. Give it the full toolbar. Then give internal notes a lighter version so nobody is distracted by buttons they never use.

Kyo Logic builds custom Claris FileMaker and manufacturing software for businesses across New England and beyond. If you want help deciding which fields deserve rich text, keeping formatted content consistent in printed and emailed output, or extending the editor with Summernote’s API, reach out.

Frequently asked questions

Does FileMaker have a built-in rich text editor?

FileMaker text fields support basic character styling from the Format menu, but there is no built-in toolbar editor with lists, headings, and links. A web viewer editor such as Summernote fills that gap.

What is the Kyo Logic Rich Text Editor built on?

It is built on Summernote, a well-documented open source editor, running inside a FileMaker web viewer.

Can I use different toolbars on different layouts?

Yes. You can create many standalone configurations, each pointing to a different field, so one can stay minimal while another offers the full set of tools.

Do I need to write new scripts for every field?

No. The communication between the editor and FileMaker is abstracted out, so adding a configuration does not require new scripts. The editor updates the field as the user types.

Quick takeaways

• Pick the one field where formatted text matters most to customers and start there.
• Use a minimal toolbar for internal notes and a full one for templates and client-facing text.
• Check how formatted content looks anywhere it leaves FileMaker, such as printed reports and emails.
• Download the add-on and set up two configurations to see the difference.