Contact NexaTools
Questions about a tool, bug reports, security disclosures, or custom web development inquiries can be sent directly to our inbox.
Email Support
Send bug reports, feature requests, privacy or legal notices, and general questions to:
Typical response time: 1 to 2 business days
Topics & Inquiries
Use a descriptive subject line so we can route your message quickly:
Bug Reports
Report broken behavior in a calculator, converter, PDF utility, or script generator.
Feature & Tool Requests
Suggest a new developer utility, file format converter, or improvement to an existing page.
Security & Privacy
Responsible vulnerability reports, data-deletion requests, or questions about our policies.
Custom Web Development
Inquire about hiring us to build a custom web application, internal utility, or frontend project.
Common Troubleshooting Steps
If a browser tool fails to load or convert a file, check these common causes before writing in:
1. Hard Refresh the Page Press
Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (macOS) to reload updated scripts and WebAssembly modules.2. Check Browser Extensions Strict script blockers or canvas-fingerprinting protections can prevent local PDF rendering or WebAssembly memory allocation.
3. Check Available Memory Local media and PDF conversions run in browser memory. Closing unused tabs helps when working with large files.
Frequently Asked Questions
Are the browser utilities on NexaTools free to use?
Yes. The browser utilities on NexaTools are free to use without creating an account or entering payment details. Fair-use rate limits apply to networked endpoints such as URL shortening and encrypted file sharing.
How does NexaTools handle my files and text inputs?
Many formatters, calculators, media converters, and PDF tools run locally in your browser using JavaScript and WebAssembly. Features that require network communication—such as URL shortening, NexaShare encrypted file sharing, NexaVault Google Drive uploads, P2P signaling, remote code compilation, disposable email, and domain/IP lookups—send the necessary inputs to NexaTools endpoints or the relevant third-party service as detailed in our Privacy Policy.
What information should I include in a bug report?
Include the tool URL, your browser name and version, operating system, the steps that triggered the issue, and any console error messages. Do not include passwords, private keys, or confidential files.
How quickly do you respond to emails?
We generally reply to support and project emails at support@nexatools.in within 1 to 2 business days.