Talk to an actual person
No ticket queue, no chatbot loop, no support tiers. Write to us and someone on the small team that builds Clippingnet will read it.
01Ways to reach us
Pick whichever fits - they all land in the same place.
General inquiries
Anything that doesn't fit the categories below.
hello@clippingnet.comBug reports
Something broke, or behaved in a way it shouldn't.
bugs@clippingnet.comFeature ideas
Something you wish the tool did that it doesn't yet.
hello@clippingnet.comBusiness & partnerships
Press, integrations, or anything business-facing.
partners@clippingnet.comTypical response time is 2–3 business days. We're a small team, so it isn't instant - but every message gets read by someone who actually works on the product, not a first-line support script.
02Or write to us directly
This opens your email client with everything filled in - nothing is sent from this page itself.
03Before you write in
A few things that make it faster for us to actually help.
Tell us the source type
Local file, direct URL, or YouTube link - the failure modes are different for each, so this narrows it down immediately.
Browser and OS
Chrome, Firefox, Safari, mobile or desktop - video APIs vary enough between browsers that this is often the actual cause.
The problem, not just the ask
"I need X" is useful; "I was trying to do Y and got stuck" is more useful, since sometimes there's already a way to do it.
04Before you write in, twice
How long does it take to hear back?
Usually 2–3 business days. Bug reports affecting a lot of people tend to get looked at faster; general feedback and feature ideas take longer since they don't block anyone from using the tool right now.
Do you offer phone or live chat support?
No - email is the only channel. The team is small enough that a live-chat queue would mean answering the same three questions all day instead of building anything.
My clip export failed - what should I check first?
Most export failures come from a direct-URL video that's on a server blocking cross-origin access (a CORS restriction), which the tool will tell you about via a status message. If you were using a local file or YouTube link and it still failed, that's worth reporting as a bug.
Can I request a feature and get an estimate on when it'll ship?
We'll tell you honestly if something's already planned, actively being considered, or unlikely to fit the tool's scope - but we don't commit to dates, since the team and roadmap are both small enough that priorities shift.
I think I found a privacy or security issue - how do I report it responsibly?
Email bugs@clippingnet.com with as much detail as you can and we'll treat it as priority. Please don't post exploit details publicly before we've had a chance to look at it.
Do you have a public roadmap?
Not a formal one right now. Given the tool's intentionally narrow scope, most requests are evaluated case by case against whether they fit "cut a clip well" rather than expanding into a general editor.
Can I contribute code or report issues on GitHub?
If a public repository is available, we'll link it from here - for now, email is the most reliable way to reach the team on anything, including code-level bugs.