Found a Problem? Let Us Know
We take every bug report seriously. Your report helps us fix issues fast — for you and every other user on the platform.
Submit a Bug Report
The more detail you provide, the faster we can fix it. Fields marked with * are required.
Thank you for reporting this. Our team will investigate the issue and work on a fix as soon as possible. Your report makes Kromo Tools better for everyone.
Our Bug Review Process
Every bug report we receive goes through a structured review and resolution process. We don't ignore reports or auto-close them without investigation. Here's exactly what happens after you submit:
Report Received
Your bug report lands directly in our team inbox. We check every business day and triage new reports within 24 hours of receiving them.
Triage & Reproduction
We attempt to reproduce the bug using the information you've provided — the tool name, browser, device, and steps. A detailed report dramatically speeds this step up.
Root Cause Investigation
Once confirmed, our development team digs into the code to find the underlying cause. We document what we find so the fix is thorough and doesn't introduce new issues.
Fix & Deploy
Critical bugs are patched and deployed within 24–48 hours. Minor issues are batched and go into the next planned update cycle. We note all fixes in our changelog.
What Makes a Good Bug Report?
The quality of a bug report directly affects how quickly we can fix the issue. Here are the elements that make a report truly useful:
- Tool name and URL — Tell us exactly which tool is affected and paste the page URL if possible.
- Specific description — Describe what happened in plain language. Avoid vague terms like "it doesn't work" — tell us what you actually saw.
- Steps to reproduce — A numbered list of what you did, step by step, that led to the bug. This is the most important part of any report.
- Expected vs actual result — Tell us what you expected to happen and what happened instead. This contrast helps us understand the scope of the bug.
- Device and browser — Many bugs are environment-specific. Knowing your browser version and device type helps us replicate the exact conditions.
- Error messages — If you saw any error messages (on screen or in the browser console), including them verbatim helps us pinpoint the issue.
How We Fix Issues
We prioritize bugs based on impact and severity. Here's a breakdown of our fix timelines:
🔴 Critical
Tool completely unusable or producing dangerously wrong output. Fixed and deployed within 24 hours.
🟠 High
Tool partially broken or consistently returning incorrect results. Fixed within 2–3 business days.
🟡 Medium
Usability or layout issues that don't block core functionality. Addressed in the next scheduled release.
🟢 Low
Minor visual glitches or cosmetic issues. Batched with other low-priority fixes when convenient.