Audio and image processing runs in your browser. There is no media upload queue, cloud storage account, or file-processing API.
Album Cover & Audio Metadata Tools
Add, extract, remove, resize, convert, and inspect album artwork. Edit MP3 metadata and cover art for MP3, FLAC, and M4A files without uploading your media.
Choose the job you need to finish
Every card opens a separate working tool with its own instructions, compatibility notes, and troubleshooting guidance.
MP3 Cover Tools
Add, recover, clear, or apply artwork across several MP3 files.
Add Cover to MP3
Add or replace embedded album artwork while preserving the original audio and other ID3 frames.
Open toolExtract MP3 Cover
Find the embedded picture in an MP3 and save the original JPEG or PNG without recompressing it.
Open toolRemove MP3 Cover
Remove embedded picture frames from an MP3 while keeping its audio and other supported metadata.
Open toolBatch MP3 Cover Editor
Apply one prepared cover to as many as 20 MP3 files and download each verified result.
Open toolMetadata Tools
Correct the text fields that players use to organize an MP3.
Cover Image Tools
Inspect and prepare artwork before embedding or publishing it.
Cover Size Checker
Inspect dimensions, aspect ratio, image format, file size, and transparency before embedding artwork.
Open toolAlbum Cover Resizer
Crop or fit artwork into square 500–3000 px outputs with format, quality, position, and background controls.
Open toolCover Format Converter
Convert as many as 20 cover images between JPG, PNG, and WebP while preserving their pixel dimensions.
Open toolOther Audio Formats
Handle embedded artwork in lossless FLAC and MPEG-4 audio.
Private tools built around real file formats
The site focuses on artwork and metadata jobs that belong together. Each tool performs a distinct operation instead of sending several keyword variations to the same interface.
Metadata tools rebuild only the required tag or container section. MP3, FLAC, and M4A audio payloads are not decoded or re-encoded.
Writers read the resulting cover or metadata back before enabling the download, so obvious write failures are reported immediately.
Audio tools read small metadata ranges where possible and join the rebuilt prefix to the original file slice. Files over 150 MB are best handled on desktop.
All current tools are free to use without registration. Your originals remain untouched, and every edit produces a separate file.
Uncommon or malformed structures are rejected instead of being rewritten optimistically. Each page explains what it supports and where players may differ.
Start with the file, then prepare only what it needs
Use the checker when you are unsure whether artwork is square, large enough, or stored in a compatible format. Resize or convert it only when necessary, then choose the matching MP3, FLAC, or M4A editor.
If a player shows unexpected artwork, extract the embedded MP3 image first. That helps distinguish file metadata from folder artwork, cached thumbnails, and online catalog matches.
Check an album cover →Frequently asked questions
Are the tools really browser-only?
Yes. The current tools use browser file APIs, typed arrays, Canvas, and local Blob downloads. Your selected audio and images are not sent to an application server.
Why does the website still make network requests?
The browser downloads the site code, styles, licensed gallery images, and privacy-focused Cloudflare analytics script. Those ordinary website requests do not include the MP3, FLAC, M4A, or custom artwork you select.
Do these tools change audio quality?
No audio encoder is used. The tools replace metadata and attach the original audio portion to the generated download.
Which tool should I use first?
Use Add Cover for one MP3, Batch Editor for several tracks sharing one image, Metadata Editor for text tags, and the FLAC or M4A page for those container formats. Use the image tools before embedding when artwork needs preparation.
Why are files over 150 MB better on desktop?
The hard audio limit is 1000 MB, but local downloads and Blob objects still depend on available device memory. Desktop browsers usually provide more memory and are less likely to suspend a long-running tab.