Contact Us
We welcome feedback, bug reports, feature suggestions, and general questions about SoundMeter Online. Whether you've encountered an issue with the tool, want to understand how our measurements work, or are interested in using the tool in an educational setting, we're here to help. Please read through this page to find the best way to get your question answered quickly.
The best way to reach us is by email. Send your message to:
hello@onlinesoundmeter.com
Please use a descriptive subject line so we can prioritize and route your message appropriately. For example: "Bug: meter freezes on Firefox 128 / macOS" or "Feature request: session recording".
What we can help with
Our team is happy to assist with the following types of inquiries:
- Bug reports — If the sound meter is displaying incorrect behavior, freezing, failing to access the microphone, or producing unexpected readings, let us know. We take bugs seriously and aim to reproduce and fix them quickly.
- Feature requests — Have an idea for a new tool, visualization, or export format? We maintain a feature backlog and prioritize based on user demand and feasibility.
- Accuracy questions — Wondering why your readings differ from a physical meter or another app? We can explain the technical factors involved and point you to our methodology documentation.
- Partnership inquiries — If you run an educational institution, acoustics consultancy, or audio equipment company and want to collaborate, we'd love to hear from you.
- Educational use questions — Teachers, professors, and curriculum designers who want to use SoundMeter Online in classroom demonstrations or lab exercises are welcome to reach out for guidance on best practices.
- Content corrections — If you spot a factual error in our blog posts or documentation pages, please let us know so we can correct it promptly.
What we cannot help with
Due to the nature of our tool and team, there are certain requests we are unable to fulfill:
- Calibration services — We do not offer calibration of physical sound level meters or certification of any measurement equipment. For calibration, contact an accredited metrology laboratory in your region.
- Legal noise documentation — Our readings are not admissible as legal evidence and we cannot provide certified noise reports for court proceedings, neighbor disputes, or regulatory complaints.
- Medical hearing advice — We are not audiologists or hearing healthcare professionals. If you suspect hearing loss or damage, please consult a licensed audiologist or ENT specialist.
- OSHA compliance consulting — Workplace noise assessments must be performed with calibrated Class 1 or Class 2 instruments by qualified occupational health professionals. We cannot advise on regulatory compliance.
- Custom development work — We do not offer paid custom development or white-label versions of the tool at this time.
How to report a bug
Good bug reports help us fix issues faster. When reporting a problem, please include as much of the following information as possible:
- Browser and version — e.g., Chrome 126, Firefox 128, Safari 17.5, Edge 126. You can find this in your browser's "About" page.
- Operating system — e.g., Windows 11, macOS Sonoma 14.5, Ubuntu 24.04, iOS 17.5, Android 14.
- Device type — Desktop, laptop, tablet, or phone. If relevant, mention the specific model (e.g., "MacBook Air M2" or "Samsung Galaxy S24").
- Steps to reproduce — Describe exactly what you did before the issue occurred. For example: "Opened the sound meter page, granted microphone access, waited 10 seconds, then the dB reading froze at 0."
- Expected behavior — What you expected to happen.
- Actual behavior — What actually happened instead.
- Screenshot or screen recording — If possible, attach a screenshot showing the issue. For intermittent problems, a short screen recording is extremely helpful.
- Console errors — If you're comfortable with browser DevTools, open the Console tab (F12 or Cmd+Option+J) and copy any red error messages you see.
The more detail you provide, the faster we can identify and resolve the problem. Vague reports like "it doesn't work" are difficult to act on without additional context.
Response time
We aim to respond to all inquiries, but response times vary depending on the type of message:
- Bug reports — Within 48 hours. Critical bugs affecting core measurement functionality are prioritized and may receive a same-day response.
- Feature requests — Within 3–5 business days. We'll acknowledge receipt and let you know whether the feature is something we're considering.
- General inquiries — Within 3–5 business days. More complex questions about methodology or accuracy may take slightly longer as we prepare a thorough response.
- Partnership inquiries — Within 5–7 business days. These typically require internal discussion before we can respond with specifics.
SoundMeter Online is maintained by a small independent team. We read every message and appreciate your patience. If you haven't heard back within the timeframes above, feel free to send a follow-up.
Before contacting us
Many common questions are already answered in our documentation. Before sending an email, you may find what you need on these pages:
- Frequently Asked Questions — Covers common questions about how the tool works, privacy, supported browsers, and microphone permissions.
- Methodology — Explains our measurement approach, including RMS calculation, A-weighting approximation, and how we handle the Web Audio API.
- Accuracy — Details the limitations of browser-based measurement and what affects the precision of readings.
- Disclaimer — Outlines what the tool is and isn't suitable for.
If your question isn't covered in those resources, don't hesitate to reach out. We genuinely want to hear from users — your feedback directly shapes the future of this tool.