Contact

Report a bug or a file that renders wrong

Contact form — this is the fastest and most useful route.

Rendering problems are much easier to fix with a file that reproduces them. If the document is not sensitive, attaching it (or a trimmed-down version that still shows the problem) turns a vague report into a fixable one. If it is sensitive, describe the structure instead: which format, roughly how large, what feature is involved (tables, embedded images, pivot tables, unusual fonts), and what you expected versus what you saw.

Useful to include:

• The file format and roughly what is in it
• Your browser and version
• What you did, what you expected, what actually happened
• Any error code shown on screen

Ask about embedding or self-hosting

Both are supported and documented:

• Embedding — see the Embed API reference for the iframe and postMessage interface.
• Self-hosting — everything runs from static files, so any web server can host a copy.

For questions that are not bug reports, the help pages may already have the answer.

Report a security issue

If you believe you have found a security problem, please do not open a public issue first. Report it privately through the contact form so it can be fixed before the details are public.

Who you are contacting

This project is built and maintained by ToolHive — see About for what that means and how to verify it. It is a personal open-source project, so replies come from a person and not a support desk: expect a real answer, but not a one-hour SLA.

What we do not need from you

Worth stating plainly, because contact pages usually collect things:

• We do not want your documents. The editor never uploads them, and support does not need them either unless you choose to attach a file to your message.
• There is no account, so there is nothing to recover, reset or delete.
• There is no mailing list. The changelog lists what shipped.