Get in Touch
We'd love to hear from you. Whether you have a question, feedback, or a feature request, please don't hesitate to reach out. PawFormatter is built and maintained by a small team, and real people read every message that comes in.
The best way to reach us is by email: contact@vlmh.work
What to write to us about
We genuinely value input from the people who use PawFormatter every day. A few examples of messages that are always welcome:
- Bug reports. If a conversion produced unexpected output or a format failed to parse, tell us what you put in and what you expected to get out. A small sample of the input (with any sensitive values removed) helps us reproduce the issue quickly.
- Feature requests. Want support for another data format, a new conversion path, or a quality-of-life improvement in the editor? Let us know. Many of the tool's current features started as a suggestion from a user.
- Questions about privacy. If anything about how PawFormatter handles your data is unclear, ask. We are happy to explain exactly what does and does not happen in your browser.
- General feedback. Praise, criticism, or a note about how you use the tool in your workflow — it all helps us prioritize what to build next.
What to expect when you write
We aim to reply to every genuine message, usually within a few business days. PawFormatter is a free project, so we cannot promise instant support, but we do read everything and take feedback seriously. To help us respond faster, please include enough detail for us to understand your situation: which formats you were working with, what browser and device you were using, and the exact steps that led to the problem.
A note on your privacy
When you email us, please do not paste confidential data such as production secrets, API keys, or personal information into your message. Because PawFormatter processes everything locally in your browser, we never see your data during normal use, and we would like to keep it that way in support conversations too. If you need to share a sample to demonstrate a bug, redact anything sensitive first. A minimal, anonymized example is almost always enough for us to help.
Before you email
Many common questions are already answered on our FAQ page, which covers privacy, supported formats, offline use, and conversion caveats. You might also find our guides useful, such as JSON vs YAML and How to convert TOML to JSON. If your question is not covered there, email us and we will be glad to help.