For general support, privacy requests, or policy questions, email us at:
To help us understand a problem without guessing, include the exact page URL, the text style or tool you were using, what you expected to happen, and what actually happened. For rendering problems, it is useful to mention the browser, operating system or device, and the destination app where you pasted the result. Unicode characters can render differently across fallback fonts, so the same output may look normal in one environment and incomplete in another.
If a particular character failed to transform, include a short reproducible example. Generator input is processed in the browser, so a small sample is usually enough to investigate an ordinary text-conversion issue.
The same contact address can be used for partnership requests, copyright concerns, and legal notices.
If a generated result looks different after you paste it somewhere else, include the source page, a short sample, and the destination where you observed the difference. The visible shape of Unicode characters depends partly on the font available in the receiving app, so a report is most useful when it identifies both environments.
For character-coverage questions, tell us which part of the input stayed ordinary or changed unexpectedly. We use those reports to compare the current engine behavior with the explanation on the page and to correct documentation when the two no longer match.
If you find an outdated statement, broken internal link, unclear instruction, or mismatch between a tool and its description, send the exact page URL and the sentence or control involved. Substantive product and documentation changes are recorded in the public updates log so visitors can see what changed.
For general questions about how styled text behaves across apps, the Unicode Font Compatibility Guide explains unsupported characters, combining marks, fallback fonts, and a practical test workflow before using decorative text in an important field.