Validate Kafka topic configuration settings. Fast, secure, and completely free. All processing happens in your browser — no data is sent to any server.
A Kafka Topic Validator checks a proposed topic name against Kafka's naming rules and common team conventions — allowed characters, maximum length (249 characters), reserved names, and whether it collides with an existing topic differing only by a dot vs. underscore (which Kafka treats as ambiguous internally and can cause metric collection issues). Kafka is more permissive about topic names than many naming convention guides assume, but a handful of hard rules and soft best-practices genuinely matter for avoiding operational headaches later.
A badly chosen Kafka topic name is the kind of mistake that's cheap to avoid up front and expensive to fix later, since renaming a topic in production usually means creating a new one, migrating consumers, and coordinating a cutover. Catching an invalid character, an overly long name, or a dot/underscore naming collision before you run kafka-topics.sh --create saves you from either a hard failure or a subtle, hard-to-diagnose metrics collision down the line.
Kafka internally replaces dots with underscores when generating certain JMX metric names, which means 'my.topic' and 'my_topic' can end up sharing the same metric name and cause confusing metric collisions — best practice is to pick one separator convention and stick to it consistently.
Topic names can be at most 249 characters and may only contain letters, numbers, periods, underscores, and hyphens — any other character will be rejected when you try to create the topic.
No, since it doesn't connect to any actual Kafka cluster — it validates the name against Kafka's general naming rules and common conventions, not against your specific cluster's existing topics.
Yes, names starting with double underscores (like __consumer_offsets) are used internally by Kafka itself, and creating a topic with a similar pattern can cause confusion or conflicts with internal tooling.
No, it's a purely offline naming-rule check that runs in your browser — no broker connection or credentials are required.