🔒 Your files stay on your device — core audio processing runs locally. Privacy details →
Find a toolCtrl K
🏷️
Free · In-browser · No upload

MP3 Metadata & ID3 Tag Editor.

Edit one MP3 or batch-tag 2–100 files. Only checked batch fields change; untouched ID3 frames, cover art and MPEG audio bytes are preserved.

Before-and-after illustration of Metadata Editor: MP3 and tags becomes Retagged MP3 through Edit ID3 fields.
Before → process → afterSee the signal story, then hear it in the workspace.

FILE STRUCTURE MAP

Tag Field Inspector

Follow audio, metadata and delivery as separate layers. Container work is easier to trust when decoded audio, editable fields and the final export are shown as distinct stages with explicit preservation limits.

Before-and-after illustration of Metadata Editor: MP3 and tags becomes Retagged MP3 through Edit ID3 fields.
MP3 and tagsEdit ID3 fieldsRetagged MP3
A file pipeline: source bytes and decoded content pass through explicit structure rules before a new, inspectable delivery is written.
Open the full signal breakdownBest source, processing logic, limits and three-pass listening check
  1. MP3 and tags

    Start with the right material

    Correcting one MP3 in detail or applying selected artist, album, year, genre or comment fields across a controlled batch.

  2. Edit ID3 fields

    Understand the transformation

    Single mode selectively rewrites changed ID3v2.3/v2.4 fields; batch mode scans tags first, changes only checked fields, leaves APIC untouched and bundles the rewritten MP3 files sequentially.

  3. Retagged MP3

    Verify the usable result

    One tagged MP3 or one STORE-method ZIP containing every output plus a JSON manifest, with unchecked frames and MPEG audio bytes preserved.

Tag completeness

Where this workflow stops

Batch cover art is intentionally never changed. The editor is MP3/ID3v2.3/v2.4-focused, refuses unsafe malformed tags, and caps the combined batch at 160 MiB on desktop or 64 MiB on mobile.

THREE-PASS CHECK

Make the final decision by ear

  • Keep the untouched original until the exported file is verified.
  • Confirm sample rate, channels, duration and metadata independently.
  • Test the delivery in the application or device that will consume it.

How to edit MP3 tags online, one file or in batch

  1. Choose Edit one MP3 for individual fields and cover art, or Batch edit 2–100 MP3s for a multi-file workspace.
  2. In single mode, load one MP3 and edit any common field; keep, replace, extract or explicitly remove its first APIC type-3 front cover. Other embedded artwork stays unchanged.
  3. In batch mode, review the queue and check each field you want to apply to every file. Unchecked fields and all cover art stay unchanged per file.
  4. Download the tagged MP3, or one stored ZIP containing all batch outputs and metadata-batch-manifest.json.

This online MP3 tag editor parses ID3v2.3 and ID3v2.4 in your browser. Changed common fields are rewritten in each source tag version; untouched raw frames keep their bytes and order, and the MPEG audio payload is copied byte-for-byte without decoding, re-encoding or uploading the track.

The batch tag editor scans only tag bytes for its queue preview, then reads valid files sequentially during export. Input is capped at 160 MiB on desktop or 64 MiB on mobile. Before creating the ZIP, a second guard estimates peak working memory against a 512 MiB desktop or 256 MiB mobile limit: retained tag buffers + retained full source buffers backing output-audio views + rewritten tag buffers + ZIP staging headers/manifest + the final stored ZIP + one conservative download-Blob copy. ZIP entries use STORE (method 0). For artwork in FLAC files, use the companion FLAC Cover Art tool.

Metadata Editor: quick answer and technical limits

Quick answer: An MP3 tag editor with a full single-file cover-art workflow and a separate 2-to-100-file batch workspace with explicit apply-mask controls.

Best for
Correcting one MP3 in detail or applying selected artist, album, year, genre or comment fields across a controlled batch.
How it works
Single mode selectively rewrites changed ID3v2.3/v2.4 fields; batch mode scans tags first, changes only checked fields, leaves APIC untouched and bundles the rewritten MP3 files sequentially.
What you get
One tagged MP3 or one STORE-method ZIP containing every output plus a JSON manifest, with unchecked frames and MPEG audio bytes preserved.

Know before you use it: Batch cover art is intentionally never changed. The editor is MP3/ID3v2.3/v2.4-focused, refuses unsafe malformed tags, and caps the combined batch at 160 MiB on desktop or 64 MiB on mobile.

Privacy: Selected audio is processed in this browser and is not uploaded to AudioWrench. Normal page assets can still be requested as described in the privacy notice. Privacy details →

FAQ

Does editing MP3 tags reduce the audio quality?
No. Only the metadata block at the front of the file is rewritten — the MP3 audio bytes are copied through completely untouched, with no decoding or re-encoding involved. The music in the saved file is bit-for-bit identical to the original.
Which tag fields and versions are supported?
The editor reads and writes ID3v2.3 and ID3v2.4 tags. You can edit title, artist, album, year, genre, track number, a comment and the front cover in single mode; frames you do not edit are carried into the saved MP3 unchanged.
Can I replace, remove or extract front cover art?
Yes. Single mode selects the first APIC picture type 3 as the front cover. Replace or remove affects only that frame; back covers and other embedded APIC artwork remain unchanged. You can also extract the selected JPEG or PNG front cover.
Is this MP3 tag editor free, and do my files stay on my device?
It is free with no account or watermark. MP3 tag parsing and writing happen in the browser, so the file is not uploaded. Untouched ID3v2.3 and ID3v2.4 frames and the original audio payload are carried through locally.
Can I batch edit MP3 tags online?
Yes. Batch mode accepts 2–100 MP3 files within the displayed input and peak-memory limits. You explicitly check each field to apply; unchecked fields, cover art, unknown frames and MPEG audio bytes remain unchanged per file. The result is one uncompressed ZIP containing uniquely named tagged MP3s and a JSON manifest.