Sleek Editor ← Open the editor

Contact

Get in touch

Questions, bug reports, ideas or business inquiries — we read every message and reply to the ones that need a reply.

Email us

The fastest way to reach the team is by email. Write to sleekeditorcontact@gmail.com and you will normally get an answer within 48 hours. If you are reporting a problem, a couple of details make a huge difference: the browser and version you are using (for example Chrome 126 on Windows 11), what you clicked right before the issue appeared, and a screenshot or short screen recording if you can. With that information most issues can be reproduced and fixed quickly.

sleekeditorcontact@gmail.com

Call or WhatsApp

Prefer to talk? Reach us directly at +92 324 3730686 — a call or WhatsApp message works equally well, and during working hours (PKT) we usually reply the same day. For anything technical, email is still the better channel because you can attach screenshots and screen recordings that help us reproduce the issue faster.

+92 324 3730686

What can you contact us about?

Bug reports

If the editor crashes, a clip refuses to behave, playback stutters or an export fails, tell us what happened and when. Your projects and media never leave your browser, so a screenshot of the timeline plus the steps you took is usually all we need to track the bug down.

Feature requests

Sleek Editor grows because of the people who use it. If a tool you need is missing — an effect, a transition, a keyboard shortcut, an export option — say so. Requests that come up again and again move to the top of the list, and several existing features started exactly this way.

Privacy and your data

Everything you create is stored locally in your own browser: media files are read from your disk, and projects autosave to local storage on your machine. If you have a question about how this works, or you want confirmation that nothing was uploaded, read the privacy policy first — and write to us if anything is still unclear.

Business, advertising and press

For partnership proposals, advertising questions, sponsorship of the editor or press inquiries, use the same email address with a clear subject line and we will route it to the right person. Include the site or product you are writing about so we can answer faster.

How to write a bug report we can act on

The difference between "it doesn't work" and a bug that gets fixed within a week is almost always the same three pieces of information. First, your environment: browser and version (Chrome 130, Firefox 132, Safari 17 and so on), operating system, and whether you are on desktop or mobile. Second, the path: what you clicked, dragged or pressed immediately before the problem appeared, in order — bugs that can be reproduced can be killed. Third, the evidence: a screenshot of the editor (the timeline and the problematic clip together are ideal) or a ten-second screen recording, plus any console errors if you are comfortable opening developer tools.

A fourth item helps disproportionately: tell us whether the problem happens in a fresh project or only in a specific one, and whether it survives a hard refresh (Ctrl/Cmd+Shift+R). Many reports turn out to be a stale cached version — the fix is simply reloading — and noting this upfront saves a round trip for both of us.

Quick answers first

Many questions are already answered on the site, and checking there first is usually the quickest route to an answer. The FAQ page covers pricing, privacy, exports, formats and browser support. The guides are step-by-step tutorials for the most common tasks — trimming, adding music, captions, transitions and more. The features page explains what the editor can do, the changelog lists what changed in every version (worth checking if something recently moved), and the terms describe how the service may be used. If the answer is missing from all of those, your email helps us improve those pages for everyone.

What happens after you write

Every message is read. Bug reports are triaged first — they affect everyone — and if a fix ships, you will typically get a reply pointing at the changelog entry that closes it. Feature requests are logged and counted; repeated requests move up the roadmap, and several shipped features began as a single email. Business inquiries get a response or a polite decline either way, usually within the same 48-hour window. One request: keep attachments reasonable in size, and never send your video files — we don't need them, and we couldn't open your locally-stored project even if you did.

Back to the editor →