Contact Us

Questions, feedback, bug reports, or feature suggestions are all genuinely welcome, here's how to reach the team directly.

Direct email

Reach the team directly at support@nearsend.app for any technical inquiries or general product support.

Quick assistance before you write in

Check the FAQ page for instant pairing tips. Make sure both devices have WebRTC enabled in their browser; it's on by default in every modern browser, but occasionally disabled by a strict privacy extension. For a restricted or sensitive local network, turning on Local-Only Mode in Settings keeps a transfer from ever leaving the local network.

What to include in a message

The contact form on this page accepts a name (optional), a reply email, a topic, technical support and connection help, a feature request or idea, a bug report, or a partnership or general inquiry, and a message describing the question or feedback in more detail.

Response times

As a small, focused project, response times can genuinely vary, bug reports and anything security-related are prioritized, while feature requests and general feedback may take longer to hear back on. Checking the FAQ and this site's blog first often answers a common question faster than waiting for a reply.

Reporting a security issue

If something looks like a genuine security or privacy issue rather than a routine bug, mentioning that clearly in the message helps it get prioritized appropriately, alongside a description of what was observed and how to reproduce it.

Feature requests and feedback

Ideas for new features, workflow improvements, or things that felt confusing during a transfer are genuinely useful, real feedback from actual sessions has shaped features like folder transfers and the three separate pairing methods offered today.

What this form doesn't cover

The contact form isn't a substitute for troubleshooting a specific failed transfer in real time, for that, the FAQ page and this site's blog cover the most common causes (network isolation, background-tab throttling, camera permission issues) in more depth than a single support reply usually can.

Business and partnership inquiries

For anything outside individual support, a partnership, a press inquiry, or a business question, selecting "Partnership / General Inquiry" on the form routes it appropriately, and including relevant context upfront helps it reach the right place faster.

Why there's no live chat or phone line

Nearsend is built and operated as a small, focused project rather than a large support organization, email is the most reliable way to reach the team directly, without the overhead of staffing real-time channels for a tool most people only need occasionally.

Language

Messages are currently handled in English only. When reaching out in another language, including a brief English summary alongside the original message helps make sure nothing gets lost in translation on either side.

Following up on a previous message

If a reply hasn't arrived and it's been a while, sending a brief follow-up referencing the original topic is completely fine; it's easier to pick a thread back up with that context than without it.

Sharing logs or screenshots

For a technical issue, a screenshot of what went wrong, or the browser's own console output if it's accessible, helps far more than a description alone; it's worth attaching whenever the issue is reproducible and a screenshot is easy enough to grab quickly.

Guides

Phone to PC Send Folders Large Files Without an App LocalSend Alternative P2P Transfer Without Shared Wi-Fi Private Sharing