Support

Support is focused on actionable, reproducible issue reports to improve turnaround and fix quality.

1. Introduction

DevUtilKit is a free tool maintained by a small independent team, and support is provided on a best-effort basis. We do not offer paid support tiers, priority queues, or formal SLA guarantees. Our goal is to respond quickly and provide technically useful guidance, but response quality depends on issue complexity and report clarity. For most problems, the fastest route to a solution is to complete the self-service checks below before sending an email. Common issues usually come from browser extensions, cached scripts, invalid input shape, or misunderstood tool limits, and the checklist addresses those patterns first.

2. Before Contacting Support

Before sending a bug report, work through these steps. In our experience, more than half of reported issues are resolved by one of the checks below. Running this checklist first saves time for you and for us, and it helps isolate whether the problem is caused by browser environment, stale assets, input validation, or an actual platform defect that requires engineering work.

- Test in a different browser. Try Chrome, Firefox, and Safari. If the issue is browser-specific, that is important information and may indicate a browser extension conflict.

- Disable browser extensions. Ad blockers, script blockers, and privacy extensions sometimes interfere with tool functionality. Disable them temporarily and retry.

- Clear your browser cache. Cached JavaScript can cause unexpected behavior after a site update. Hard refresh: Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows).

- For SQL Runner specifically: confirm your query is a valid SELECT statement. SQL Runner does not accept INSERT, UPDATE, DELETE, DROP, or any other write or DDL statement. If your query starts with anything other than SELECT or WITH (for CTEs), it will be rejected.

- For JWT Decoder specifically: confirm the token has exactly three dot-separated sections (header.payload.signature). A string with fewer than two dots is not a valid JWT.

3. How to Report a Bug

If you have worked through the checklist above and the issue persists, please send a bug report. A useful report includes enough information for us to reproduce the problem without multiple follow-up questions. Reproducible reports reduce triage time significantly and let us verify whether the issue is deterministic, environment-specific, or data-shape-specific before we propose a fix.

- Tool name (e.g. JWT Decoder, SQL Runner, JSON Formatter, Base64 Converter)

- The exact input you used, or a representative sample that reproduces the issue

- What you expected to happen and what actually happened (include errors verbatim)

- Your browser name and version, and your operating system

Email: support@devutilkit.com — Subject: Bug: [Tool Name]. If sensitive data is involved, please redact personal records, tokens, and credentials before sending your sample.

4. Feature Requests

We welcome suggestions for new tools and improvements to existing ones. The most useful requests describe the real problem you are trying to solve, not just a feature label. For example, saying that you need a reliable way to convert cron expressions into human-readable schedules is more actionable than saying add cron tool. Requests with context such as team workflow, expected input/output format, and current pain points help us prioritize roadmap items that create measurable value for developers. Email support@devutilkit.com — Subject: Feature Request: [Description].

5. Response Time