U UtilityHub
Support & Technical Inquiries

Contact UtilityHub

Encountered an unusual file encoding issue, discovered an algorithmic bug, or have ideas for a new utility? We welcome direct, technical feedback.

1. Official Contact Channel

UtilityHub deliberately does not use third-party contact form submission widgets or webhooks that collect tracking identifiers or store messages on third-party servers. All communications take place directly via email.

Preview Deployment Notice

Public Preview Deployment

UtilityHub is currently accessible as a public preview deployment on Cloudflare Pages for verification and technical testing. Direct public contact channels and formal support mailboxes will be officially published alongside custom domain provisioning in Step 21.

For technical issues or verification inquiries during this preview phase, configure the PUBLIC_CONTACT_EMAIL build environment variable or contact the maintainers via the code repository.

2. Structured Inquiry Categories

To help us diagnose and resolve your question as quickly as possible, please select the relevant category when emailing:

Category A: Bug Reports & Parsing Failures

Tool Failures or Crashes

If a tool fails to parse a valid file, freezes the tab, or produces unexpected errors. Please include:

  • Tool name and URL (e.g. JSONL to CSV).
  • Your operating system and browser version (e.g. Chrome 124, Windows 11).
  • A short sanitized or redacted sample snippet reproducing the failure.
  • Any console error messages visible in Developer Tools (F12).
Category B: Formatting & Character Encodings

Edge Case Data Dialects

Questions regarding complex CSV delimiters (semicolons, ASCII record separators), legacy code page encodings (Windows-1252, ISO-8859-1), or multi-byte UTF-8 character handling.

Category C: Privacy & Architecture Inquiries

Client-Side Isolation & DPDP

Inquiries regarding client-side data isolation, WebAssembly memory sandboxing, the Terms of Service, or DPDP Act compliance clarifications.

Category D: Tool Suggestions & Ideas

New In-Browser Utilities

Have an idea for an everyday developer, text, or data conversion utility that would benefit from client-side execution? Let us know what pain point it solves.

3. Before You Contact: Self-Service Troubleshooting

Many common tool issues can be resolved immediately with these quick diagnostic steps:

1
Disable Conflicting Browser Extensions:

Certain grammar checkers, translation extensions, or ad blockers inject scripts into webpage textareas that interfere with high-volume paste operations. Try reproducing the action in an Incognito / Private window.

2
Inspect the Browser Console:

Press F12 or Ctrl+Shift+I (Cmd+Option+I on macOS) and navigate to the "Console" tab. Any memory exhaustion errors or parsing syntax errors will be highlighted in red.

3
Verify File Size and Free Memory:

Files exceeding 100MB–200MB can occasionally trigger tab memory exhaustion in memory-constrained devices. If your browser tab crashes unexpectedly, test with a smaller slice of your dataset first.

4
Confirm Text Encoding:

Ensure files are saved with standard UTF-8 encoding. If your file contains unusual characters from Excel exports, run it through our CSV Separator & Encoding Fixer first.

4. Response Expectations

UtilityHub is maintained as an independent web utility project. We review messages regularly:

  • Security & Vulnerability Reports: Prioritized and acknowledged promptly upon verification.
  • Bug Reports & Edge Cases: Investigated and addressed on a best-effort basis during active maintenance cycles.
  • Feature Requests: Reviewed during regular development cycles.