Get in Touch

Questions, bug reports, feature ideas, or just want to say hello — we're happy to hear from you.

🐛

Bug Report

Found something broken? Let us know the tool name, what you expected to happen, and what actually happened. Screenshots help.

Reply within 1–2 days

💡

Feature Request

Want a new tool or an improvement to an existing one? Describe the use case and we'll add it to the roadmap.

Reply within 1–2 days

🤝

Partnerships

Interested in collaborating, sponsoring, or linking to CSSTools.io? Reach out with your proposal.

Reply within 3 days

📝

General Feedback

Something on your mind about the site? All feedback is welcome — positive or constructive.

Reply within 2–3 days

Support Information

CSSTools.io is maintained by a small independent team. Use the details below to reach us for any of the topics above.

✉️

Support Channel

Send your message to our support address: support@csstools.io
Include the tool or page name and a brief description of your question or issue.

🕐

Response Time

We aim to respond to all messages within 1–2 business days. High-volume periods may occasionally take a little longer.

🌍

Language

We respond in English. Messages in other languages are welcome — we'll do our best to assist.

Common Questions

Are all the tools really free?

Yes, completely free with no account required. All tools run in your browser. There are no paid tiers, no watermarks on generated code, and no limits.

Can I use the generated CSS in commercial projects?

Yes. The CSS you generate is yours to use in any project — personal, commercial, open-source or client work — without attribution.

A tool is not working on my browser — what should I report?

Please include: the tool name, your browser name and version (e.g. Chrome 124), your operating system, and a description of what happened vs. what you expected. A screenshot is always helpful.

Can I request a new CSS tool?

Absolutely — new tool suggestions are how the site grows. Describe the CSS property or effect you'd like a visual generator for and we'll evaluate it for the roadmap.