Contact Us

Questions, bug reports, business enquiries – pick the route below that fits and we will get back to you.

Help and bug reports

A style that will not copy, a tool that returns nothing, a character that shows as an empty box. Also the right place for suggesting a font style or a tool you wish the site had.

Email support

classstatus0@gmail.com

Business and privacy

Partnerships, advertising and licensing. Also the route for anything about your data – a copy of what we hold, or a deletion request under the privacy policy.

Email us

classstatus0@gmail.com

Developers

Using the JSON API or the npm package? The developer docs cover the endpoint, its parameters and the error codes. Package bugs are best raised as issues, where they are public and get a version number attached.

Open an issue

github.com/ClassStatus

What to include

  • The page you were on. Paste the address – the site has more than sixty tools and most reports could be about any of them.
  • The text you typed and the style you picked. A character that breaks in one style usually works in the other three hundred.
  • Where you pasted it. Instagram, Discord and Word each drop different characters, and that is normally the whole explanation.
  • Your browser and device. "Chrome on Android" is enough; a missing glyph is far more often the font on the device than the site.
Before you write: if characters show as boxes or question marks after pasting, that is the receiving app missing the font, not a fault here – the same text will look right somewhere else. Try a plainer style, or use the PNG text generator, which renders to an image that looks identical everywhere.

We read everything and reply to most messages within a couple of working days. This is a small operation, not a support desk – if something is urgent, say so in the subject line.

If you are after a particular tool rather than a person, the font generator and the png text generator are the two busiest pages on the site.

Frequently asked questions

Usually within two working days. Bug reports with enough detail to reproduce the problem tend to be answered fastest, because they need no back-and-forth.

The page address, what you did, what you expected and what happened instead, plus your browser and device. A screenshot settles most questions immediately. If a tool produced the wrong output, include the exact text you typed in.

Yes, and they are welcome. Tell us what you would use it for rather than only what it should do - the use case is usually what decides whether it gets built and how.

No. Please do not send these - they will not be answered. Genuine business enquiries about the site itself are welcome.

Write to us through this page and say it concerns privacy in the subject line. Most tools here never send your text anywhere, so if you are worried about something specific, tell us which page and we will explain exactly what it does.

Often it is not. If characters appear as empty boxes, your device is missing a font for them rather than the tool being broken. It is still worth telling us which device and which style, because it helps us warn other people.