Local browser tools for images, video, and audio
Convert, resize, clean up, and export media without leaving your device.
Picmu is built around real jobs: image conversion, file-size reduction, crop, print prep, metadata cleanup, batch export, careful browser video workflows, and audio tools with waveform checks and clear alternatives.
Focused media tools, not a vague all-in-one editor.
Picmu keeps privacy, page-specific guidance, and output details 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 version of Picmu that fits how you work.
All seven versions use the same tools, privacy model, and page structure. You are choosing the language, not a smaller version of the product.
Main product language
English
Open Picmu in English, with English navigation, guides, FAQ, and support pages.
- Best if you want English URLs and product terms.
- Includes the full image, video, audio, guide, FAQ, and support library.
- Easy to compare with the Russian version if you use both.
Russian interface
Русский
Use Picmu in Russian with the same tools, privacy model, and browser checks.
- Russian navigation, labels, guides, FAQ, and support copy.
- The same image, video, and audio workflows as the English version.
- You can switch back to English at any time.
Spanish interface
Español
Use Picmu in Spanish with the same tools, privacy model, and browser checks.
- Spanish navigation, labels, guides, FAQ, and support pages.
- The same image, video, and audio workflows as the other localized versions.
- You can switch languages without losing the matching page path.
Portuguese interface
Português
Use Picmu in Portuguese with the same tools, privacy model, and browser checks.
- Portuguese navigation, labels, guides, FAQ, and support pages.
- The same image, video, and audio workflows as the other localized versions.
- You can switch languages without losing the matching page path.
French interface
Français
Use Picmu in French with the same tools, privacy model, and browser checks.
- French navigation, labels, guides, FAQ, and support pages.
- The same image, video, and audio workflows as the other localized versions.
- You can switch languages without losing the matching page path.
German interface
Deutsch
Use Picmu in German with the same tools, privacy model, and browser checks.
- German navigation, labels, guides, FAQ, and support pages.
- The same image, video, and audio workflows as the other localized versions.
- You can switch languages without losing the matching page path.
简体中文界面
简体中文
使用简体中文打开 Picmu，工具、隐私模型和浏览器检查与其他版本一致。
- 简体中文导航、标签、指南、常见问题和支持页面。
- 图片、视频和音频工作流与其他本地化版本一致。
- 切换语言时会保留对应页面路径。
Why Picmu
A clearer way to handle media in the browser.
Picmu is built around privacy, task-specific pages, and support notes written in plain language.
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
Start on the page built for 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
Browser limits show up early.
Video pages show capability checks early, so you can see what export options this browser supports.
Ready for handoff
Made for the jobs people actually do.
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 expands around work people actually need to finish. Image pages go deeper, video pages stay careful about export support, and audio pages keep waveform checks and browser limits visible.
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 which other output 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 alternate outputs.
- 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 useful when full browser 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 being pushed through a generic cloud editor.
Start on the right page.
Pick the 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 to finish media tasks without uploading every file.
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 account walls, vague all-in-one editor claims, and unclear capability language.
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, Russian, Spanish, Portuguese, French, German, and 简体中文, 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 one-size-fits-all converter.
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 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 implying 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 offer another output 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 option 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. Pages explain the important tradeoffs before export.
Will transparency survive every image conversion?
No. Transparency depends on both the source and the target format. When a page exports to an opaque format, Picmu calls out 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?
You can still get useful output. Frame capture lets you save a still image locally and continue in 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 all-purpose screen. That means clearer defaults, visible capability notes, and fewer surprises while you work.
What does Picmu show after processing finishes?
Picmu shows the local result with the output format, filename, size change, relevant dimensions, and the next useful page when you want to keep refining the file.
Start with the right page
Open Picmu and keep the work on your device.
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.