Contact
Direct contact with Sergei Solod for route issues, serious feedback, and practical product questions.
Picmu is an independent product built by Sergei Solod, so your message does not disappear into a generic support queue. If a route breaks, browser support behaves differently than expected, copy feels unclear, or you want to discuss business use, the message goes straight to the developer. You can also learn more about his background at jsvar.com.
Direct contact
Send a message to the developer
Use the form for route questions, browser capability issues, licensing, business conversations, or a concrete bug report. It goes directly to Sergei Solod.
Direct email
sergeissolod@gmail.comUse email when the conversation is easier to track outside the browser, especially for partnerships, licensing, legal questions, or business use. It goes directly to Sergei Solod.
For technical issues, include the route, browser, device, source format, target format, and whether the problem happened before export, during export, or after download.
Contact
What to write about
The fastest messages are concrete and tied to a real route, browser, and outcome.
Product or workflow question
Ask when you are unsure which route fits the job, what a capability note means, or how a specific output is intended to behave.
Bug report or browser mismatch
Useful for broken exports, incorrect previews, odd codec behavior, performance regressions, and feature differences across browsers or devices.
Business or licensing
Use direct contact for commercial use, partnerships, licensing conversations, or situations where the message should be tracked outside the site.
Content correction or trust issue
Send a note if copy feels misleading, outdated, confusing, or simply not good enough for a product that is trying to be clear.
Picmu
What helps the message land well
A little structure makes it much easier to reproduce a problem or answer a real product question without guessing.
Who reads these messages
Messages go directly to Sergei Solod, the developer behind Picmu. That keeps support direct and makes it easier to discuss a real route, bug, or product decision without a layered handoff.
If you want broader background before reaching out, jsvar.com covers his experience, resume, and other developer work.
For image routes
Include the route path, source format, expected output format, whether you used batch mode, and what happened visually or in the final download.
If the issue is about print, target size, transparency, cleanup, or metadata, mention the exact setting that looked wrong or behaved differently than expected.
For video routes
Mention the browser, operating system, container or codec when you know it, and whether the issue appeared in preview, capability checks, trim or crop interaction, or export.
Video bugs are much easier to reason about when the message includes the route, the source file type, and whether the browser failed to decode, encode, or save the result.
For UX, copy, or trust issues
If a route feels unclear, noisy, or misleading, say where it happened and what expectation the page created for you.
That kind of feedback matters because Picmu is deliberately built around calm interfaces and honest wording, not just raw feature count.
For business, licensing, or legal context
If the message is commercial or legal in nature, say that early and keep the request specific. It helps route the answer faster and keeps the thread easier to track.
If attachments or sample files are necessary, start with context first and avoid sending sensitive material in the initial message.
Tools
Want to go back into the route library?
Open the media route index to jump from feedback into image hubs, video hubs, and the exact workflow pages.
FAQ