Local browser tools for images, video, and audio
Convert, resize, clean up, and export media on your device.
Picmu is built around real jobs: image conversion, file-size reduction, crop, print prep, metadata cleanup, batch export, careful video handling in the browser, and audio tools with waveform checks and clear fallbacks.
Built for real media jobs, not generic editor hype.
Picmu keeps privacy, page-level clarity, and output logic visible from import to export, whether you are preparing images, testing a browser video path, or checking audio before you commit.
Language selection
Choose the Picmu version that matches how you work.
Both versions keep the same tools, privacy model, and page structure. You are choosing the language layer, not a cut-down version of the product.
Main product language
English
Open the main English version with the default product terminology, guides, and UI copy.
- Best if you want English URLs and the default product naming.
- Includes the full set of image, video, audio, guide, FAQ, and support pages.
- Useful as the reference version when you compare English and Russian copy.
Russian interface
Russian
Use Picmu in Russian with the same tools, privacy model, and browser checks.
- Russian navigation, guidance, and supporting copy across the product.
- The same image, video, and audio workflows as the English version.
- Easy to switch later if you want to compare the two versions.
Why Picmu
A calmer way to handle media in the browser.
Picmu is built around privacy, task-specific pages, and support notes that say exactly what they mean.
Local first
Your files stay with you.
Core image work, video checks, and audio handling stay on your device instead of running through an upload queue.
Task-first pages
Open the tool that fits the job.
Conversion, compression, resize, print prep, cleanup, batch export, video tasks, and audio tasks each start from their own page.
Video with reality checks
Limits are called out early.
Video pages start with capability checks and clear fallbacks instead of pretending every browser can export every codec.
Built for actual handoffs
Made for everyday media work.
Use Picmu for format changes, smaller files, print prep, marketplace images, frame capture, speech-first audio work, and other routine jobs.
Workflow coverage
Deep image coverage, careful video handling, and audio tools that show their limits.
Picmu grows from useful jobs instead of fake feature sprawl. The image side goes deeper. The video side stays careful about support, export limits, and fallback value. The audio side adds waveform checks without losing that same honesty.
Image tools
Image workflow hub
Start from the job you actually have: format conversion, compression, resize, crop, cleanup, print prep, metadata removal, or batch export.
Practical format pairs such as PNG to JPG, JPG to WebP, WebP to PNG, and AVIF to JPG.
Compression, resize, crop, upscale, print prep, artifact cleanup, and batch conversion stay separate.
Metadata cleanup, background fill, social resizing, watermarking, favicon generation, and more.
Supporting content that explains transparency, print sizing, compression tradeoffs, and batch logic.
- PNG to JPG, JPG to WebP, WebP to AVIF, AVIF to PNG, and more.
- Compress image, resize image, crop image, image for print, and batch image converter.
- Metadata cleanup, background fill, marketplace assets, social sizes, and favicon generation.
Video tools
Video workflow hub
Start with the browser question that matters: what can this runtime decode, preview, or export safely, and what fallback still gets the job done?
Video conversion, compression, resize, trim, crop, mute, audio extraction, and frame extraction.
Dedicated pages such as MP4 to WebM, WebM to MP4, and MOV to MP4.
Poster-frame capture plus focused pages for WhatsApp, Telegram, and marketplace delivery.
Browser support, playback tradeoffs, container choice, trimming limits, and fallback logic.
- Video converter, compress video, resize video, trim video, crop video, and mute video.
- MP4 to WebM, WebM to MP4, and MOV to MP4 where pair-specific logic matters most.
- Frame capture remains a dependable fallback when full browser-native export is uneven.
Audio tools
Audio workflow hub
Start from the browser question that matters: can this runtime preview the source, decode it for waveform analysis, and safely export the target you want?
Audio conversion, compression, trim, merge, gain, normalization, speed, metadata inspection, waveform inspection, and batch export.
Dedicated pages such as MP3 to WAV, M4A to WAV, WAV to Opus, and WAV to M4A.
Preset-led pages for WhatsApp, Telegram, podcasts, voice notes, ringtones, mono downmix, and metadata cleanup.
Guides for browser limits, format choice, speech-safe compression, trimming, and local processing logic.
- Audio converter, compress audio, trim audio, merge audio, change volume, normalize audio, and waveform inspection.
- MP3 to WAV, M4A to WAV, WAV to Opus, and WAV to M4A where pair-specific logic matters most.
- Voice-note trim, podcast compression, ringtone-making, mono downmix, metadata cleanup, and queue-based batch export.
How Picmu works
Clear pages, visible tradeoffs, and local output.
Picmu is designed to feel direct. You arrive with a media task, pick the closest page, understand the limits early, and export without getting dragged into a generic cloud-editor flow.
Start with the exact job.
Start with the exact page that matches the outcome you need: convert, compress, resize, clean up, prep for print, trim audio, inspect a waveform, or capture frames.
Check the limits early.
Picmu surfaces transparency rules, print constraints, browser support, waveform limits, and export tradeoffs before you commit.
Export locally and move on.
Finish on your device, review the result, and jump straight to the next relevant page if the job keeps going.
About Picmu
An independent product built around clarity, privacy, and trustworthy output.
Picmu is built by Sergei Solod around one simple idea: everyday media work should feel calm, precise, and trustworthy.
What Picmu stands for
Picmu is an independent browser-based media toolkit by Sergei Solod for people who want real work done without turning every file into an upload.
It is deliberately page-based: conversion, print prep, cleanup, batch work, video checks, and audio work all get their own defaults and guidance.
The product avoids vague all-in-one editor promises, account walls, and inflated capability claims.
Why clear task pages matter
A resize job is not the same as a PNG-to-WebP conversion, a poster frame is not the same as a full video export, and an audio trim page is not the same as a batch converter. Picmu separates those jobs so the copy, defaults, and next steps stay aligned with the outcome.
English and Russian, same product logic
The language layer changes the copy and labels. The product model stays the same: local-first image work, careful video pages, audio pages with visible limits, and clearer tradeoffs than a generic converter page.
FAQ
Questions people ask before trusting browser-based media tools.
This FAQ covers the practical questions that matter for privacy, image conversion, print prep, batch work, browser video export, and browser audio export.
Does Picmu upload my files to a server?
No. Picmu is built around local browser processing for its core workflows, so your files stay on your device instead of being sent through a remote media pipeline.
Do I need an account to use Picmu?
No. Core image tools, browser-aware video workflows, and browser-native audio workflows are designed to work without account walls, upload queues, or a remote editor model.
Can Picmu handle images, video, and audio?
Yes. Picmu combines image conversion, compression, resize, crop, print prep, metadata cleanup, and batch export with video tools for conversion checks, compression, trim, crop, mute, audio extraction, and frame capture, plus audio tools for conversion, compression, trim, merge, gain, normalization, waveform inspection, metadata cleanup, and batch export.
Does every browser support every local video workflow?
No. Video support depends on the browser, container, codec, decode path, and export path. Picmu makes those constraints visible instead of pretending local video support is universal.
Does every browser support every local audio workflow?
No. Audio support depends on the browser's playback, decode, offline rendering, and export path. Picmu separates those states so a playable file does not get mistaken for a fully editable one.
Why do some video pages show a fallback instead of full export?
Because preview, decode, and export support are not always the same thing. When a browser cannot finish a reliable video export, Picmu keeps a useful fallback visible, such as still-frame capture.
Can Picmu convert every image format pair?
Not always. Picmu covers many practical format pairs, but some conversions still depend on browser support, source features, and output constraints. The page should explain any meaningful tradeoffs.
Will transparency survive every image conversion?
No. Transparency depends on both the source and the target format. When a page leads to an opaque format, Picmu should surface the alpha-loss tradeoff before export.
Does conversion or recompression improve image quality?
No. Conversion changes compatibility and output behavior. Compression reduces file size with tradeoffs. Neither one creates detail that the source file does not already contain.
Does 300 DPI add detail to a small image?
No. DPI does not create new pixels. Print readiness depends on real source dimensions and intended print size, which is why Picmu ties print checks to actual pixel data.
Can I batch process images in Picmu?
Yes. Picmu supports queue-based image workflows so you can import multiple files, apply shared settings, override a selected item when needed, and export the result as a ZIP archive.
What happens when full video export is blocked?
Picmu can still remain useful. One of the strongest fallbacks is frame capture, which lets you pull a still image locally and continue into image tools for resize, cleanup, watermarking, or format conversion.
Is WebP or AVIF always the best output format?
Not automatically. Newer formats can reduce file size, but the right choice still depends on transparency, compatibility, browser support, visual goals, and where the file will be used.
What makes Picmu different from a generic converter page?
Picmu is built around task-specific pages instead of one vague all-purpose screen. That means clearer defaults, more honest capability messaging, and a more reliable path through real media work.
What does Picmu show after processing finishes?
Picmu should show a clear local result state with the output format, filename, size change, relevant dimensions, and the next most useful page if you want to keep refining the file.
Start with the right page
Open Picmu and keep the work local.
Choose your language, go straight to the image, video, or audio hub, and use a page that matches the job instead of guessing inside a generic editor.