Contact

Questions, feedback, or partnership ideas? We’d love to hear from you.

Email

The fastest way to reach us is by email: everydayroyalties@gmail.com

What to include

Response time

We typically reply within 1–2 business days.

Optional contact form

Note: This form opens your email client to send the message. If it doesn’t work on your device, email us directly.

Support

What We Can Help With

We cannot offer formal acoustic consulting or legal advice, but we do pay attention to patterns in the questions people send. If many people struggle with the same concept—such as combining sources or understanding exposure tables—we often turn that into a clearer guide or example on the site.

When you reach out, it helps to describe your environment in simple terms: the type of space, distance to the main source, rough reading range, and what you are hoping to decide. That context makes it easier for us to point you toward the most relevant articles on the site.

Expectations

Response Times and Boundaries

We cannot promise individual replies to every message, especially when volumes are high. When we do respond, replies are meant as general pointers, not personalized engineering advice. If you require detailed analysis or official reports, you may need to work with an acoustics professional in your area.

Even when we cannot respond directly, your feedback still matters. Recurring questions influence which topics we cover next and how we explain complex ideas.

What not to include

Information We Recommend Leaving Out

To protect your privacy, avoid sending full addresses, detailed schedules, or recordings of other people's conversations when you describe a sound issue. General descriptions—such as the type of building, approximate room size, and time of day—are usually enough to point you toward relevant resources.

Ideas

Suggesting Topics You Would Like to See Covered

If there is a specific scenario you wish we explained—a type of venue, a home layout, or a work pattern—you can mention it briefly in your message. While we cannot promise individual guidance, we do use these suggestions when choosing which articles or examples to develop next.

Classroom use

Using the Meter in Educational Settings

Teachers and instructors have used the online decibel meter as a hands-on demonstration tool in physics, health science, and environmental studies classes. Because the tool runs in any browser without installation, it works on school Chromebooks, shared laptops, and tablet carts without requiring IT approval or software downloads. Common classroom uses include demonstrating the logarithmic nature of the decibel scale by measuring progressively louder sounds, comparing the level of different classroom environments before and after acoustical changes, and introducing students to occupational health concepts around hearing protection. If you are developing a lesson plan around the tool and would like to suggest additional features useful for education, we are particularly interested in hearing those requests.

Research use

Using the Meter for Research and Citizen Science

Researchers and community advocates have used browser-based decibel meters as a low-cost complement to professional monitoring in noise mapping projects, neighborhood noise documentation efforts, and environmental justice campaigns. While the readings do not meet the calibration requirements of formal acoustic surveys, consistent measurements taken with the same device at the same positions over time can identify meaningful trends and patterns. If you are using the tool as part of a larger data collection effort and find limitations that affect your project — specific frequency response information, data export format, or measurement statistics — please describe what you need. Some of these are technically feasible additions and user research needs help us prioritize them.

Accessibility

Accessibility and Device Compatibility

The tool is designed to function on a wide range of devices with minimal barriers. The interface uses semantic HTML and standard keyboard navigation. Color contrast meets WCAG AA standards throughout. The meter's gauge and chart include ARIA labels for screen reader users. If you encounter a specific accessibility barrier — with the controls, the visual display, or any page content — please describe it in as much detail as possible so we can address it. We are also interested in hearing from users who primarily access the site on older devices, low-end smartphones, or in low-bandwidth environments, as performance considerations for those contexts are easy to overlook when developing primarily on modern hardware.

Common Questions

Is the microphone audio sent to any server?

No. All audio processing happens locally in your browser using the Web Audio API. No audio data, dB readings, or measurement history is transmitted to any server. The microphone permission is only active while the meter is running — you can revoke it any time in your browser settings.

How accurate is a browser microphone meter vs a dedicated instrument?

Browser-based meters are accurate to approximately ±2–5 dB for relative comparisons — useful for identifying loud sources and before/after comparisons. For OSHA compliance, legal noise disputes, or professional hearing conservation programs, a certified Type 1 or Type 2 sound level meter with calibration records is required.

What browsers and devices support the meter?

The meter works on any modern browser supporting the Web Audio API: Chrome 47+, Firefox 44+, Edge 79+, Safari 14.1+. iOS Safari requires a tap to start the microphone due to Apple's autoplay policy. If the meter doesn't start, check that your browser has microphone permission enabled for this site in your device settings.

How does the calibration offset work?

The calibration offset shifts all readings by a fixed dB value to account for your microphone's sensitivity variance. To find your offset, compare your reading against a known-level source or a reference meter at the same position, then enter the difference. This doesn't make the meter laboratory-accurate but meaningfully improves consistency for repeated comparisons on the same device.

How do I report a bug or request a feature?

Email everydayroyalties@gmail.com with "Bug Report" or "Feature Request" in the subject. For bugs, include your browser, device, OS, and what you expected vs what happened. For feature requests, describe the measurement task you're trying to accomplish. Most current features — calibration offset, CSV export, A/C/Z weighting — came from user requests.

Can I embed this meter on my own website?

We do not currently offer an embeddable widget version of the meter. If you would like to link to the tool from your site, a standard hyperlink to online-decibel-meter.netlify.app is the simplest approach. If you have a specific embedding use case — a classroom platform, a research portal, or an educational resource site — describe it in an email and we can discuss what options might be workable.

Why does the meter show different readings on different devices?

Every microphone has its own frequency response curve and sensitivity level. A laptop microphone, a phone microphone, and a tablet microphone will all produce somewhat different readings for the same sound in the same room. This is expected and normal. For consistent comparisons over time, use the same device in the same position. The calibration offset allows you to account for your specific device's sensitivity offset from a reference level, improving the usefulness of absolute readings on your particular hardware.