Neatbo.

Make file edits auditable

A reliable local edit states the actual persisted tags, source-frame maps or removed revision structures.

A renamed file may still sort incorrectly

A cheap player may sort by ID3 Title while the visible filename already has the correct leading track number. The required output is a real MP3 copy with a changed persistent tag. Default Title {track} - {title}.mp3 carries the original filename track spelling; numeric TRCK alone does not reproduce that demand.

Separate the evidence
LayerWhat to check
Filename templateExplicit tokens/delimiters match the selected filename
Persistent ID3 valuesIndependent reader sees the new Title/artist/track
Opaque tags/audioArtwork/custom raw frames and MPEG SHA remain equal

Reject ambiguous or lossy legacy edits

An explicit template is a user decision, not a heuristic guess. Its first-literal delimiter policy must be visible so a title containing the delimiter is caught during review. Likewise, a Unicode title cannot fit ID3v1 Latin1: failing strict sync preserves the opportunity to choose strip or a compatible title rather than silently losing characters.

  • Keep the original files.
  • Use complete before/after JSON/CSV, not just the browser preview.
  • Confirm the player reads the edited copy; do not infer its sorting behavior from the filename alone.
  • Cancellation or one bad input yields no partial success ZIP. Correct the named source and rerun.

Retain the true time and structural handoff

CUE times become indexes on a real decoded recording. A pregap policy changes who receives those frames and must be reported. MP3 decoder timing can vary; choosing browser-local PCM means reporting the actual rate/frames and verifying quantized tracks against those samples, rather than promising identical ends across browsers.

DOCX hiding and structural deletion are different deliverables. A safe strict subset preflights every part and rejects unsupported history before discarding anything; accepting a text branch cannot bypass an unsupported property change hidden inside a deleted branch. Actual comments relationships and types must be removed with the target parts.

Audit the delivered artifact
TaskEvidenceRemaining boundary
CUEFull75fps-to-sample map, every retained quantized frameBrowser MP3 gapless and source-format quantization
DOCXActual new/old text, removed comments/settings, unchanged partsComplex revisions refused; metadata/forensic erasure not certified

Choose complete failure accounting

These edits produce a complete output set or fail. A bad CUE index, malformed FLAC frame, unsupported DOCX history or batch tag failure is not repaired by quietly omitting the problem. Correct the identified input and rerun after cancellation; keep originals and complete downloaded mappings.

References

Tools in this category

Expand a tool to see its steps, options and supported formats, then open its workspace.

Filename-template MP3 tag editorPersist composed MP3 titles, artists and track numbers from an explicit filename template while preserving MPEG and unrelated tag frames.

Choose MP3s and declare how filenames map to track, title and artist. The default persisted Title keeps the zero-padded filename track followed by title and .mp3, useful for players that sort by Title. Download edited copies and the complete before/after report.

Steps

  1. Choose MP3 files and set explicit filename/Title templates.
  2. Choose ID3v1 removal or strict Latin1 synchronization.
  3. Review persisted before/after tags and original MPEG SHA; download ZIP.

Available options

Filename input template
{track} - {title} - {artist}.mp3
Persisted Title template
{track} - {title}.mp3
Legacy ID3v1 policy
Remove ID3v1 · Synchronize strict Latin1

Capabilities and limits

  • 200 files,30 MiB each,80 MiB total;ID3 tag≤1 MiB/file, complete outputs≤100 MiB. A failure or cancellation rejects the whole batch. Ordinary unflagged ID3v2.3/v2.4 only; v3 writes UTF16LE+BOM, v4 UTF8.
  • Change only TIT2/TPE1/TRCK. Other raw frames including multiple APIC/TXXX and original MPEG bytes are retained. Duplicate edited frames, inner-NUL multi-values, v3 multi-artist slash values, unknown flags, compression/encryption/unsynchronization/extended headers/footer reject. Each token ends at the first following literal delimiter; choose a less ambiguous template when names contain it.
Open Filename-template MP3 tag editor →
CUE-index recording splitterSplit one WAV, MP3 or raw FLAC recording at explicit CUE indexes and export PCM16 WAV tracks with complete source-frame mappings.

Select one audio file and its UTF8 CUE. FILE must match the selected name; choose how INDEX00 pregaps are assigned. Every track becomes a numbered WAV, with titles, original indexes, retained frame ranges and dropped leading/pregap frames in the complete report.

Steps

  1. Choose matching CUE and audio files.
  2. Choose previous/next/discard pregap handling and inspect all source-frame mappings.
  3. Download numbered PCM16 WAV tracks and full JSON/CSV.

Available options

Pregap handling
Assign to previous track · Assign to next track · Discard pregap frames

Capabilities and limits

  • Exactly2 files: audio30MiB plus CUE1MiB,31MiB total; decoded float32 storage80MiB,99 tracks, complete outputs100MiB. Rate8–192kHz,1–8 channels. A budget error or cancellation rejects the whole output.
  • Single FILE, increasing TRACK1–99 AUDIO, TITLE/PERFORMER and INDEX00/01 at75fps; printable ASCII REM comments are retained only as opaque ignored comments. Other directives/multiple FILE/duplicate/empty/out-of-range tracks reject. Raw FLAC requires known STREAMINFO total frames, metadata≤8MiB/1000blocks, unchanged rate/depth/channels, valid frame structures and CRC8/CRC16. Ogg FLAC and unknown-size streams reject; STREAMINFO MD5 is not independently verified.
Open CUE-index recording splitter →
Finalize DOCX text revisions and classic commentsAccept or reject supported DOCX run-level text revisions, delete classic comment structures and stop future revision tracking.

Choose an ordinary DOCX and a finalization policy. Accept keeps inserted text and removes deleted text; reject keeps deleted text as ordinary text and removes insertions. Classic comments, their actual relationship targets and content-type declarations are removed. Keep original files for review.

Steps

  1. Choose DOCX and accept or reject all supported text revisions.
  2. Review full story counts, removed comment parts and tracking settings.
  3. Download the real final DOCX and complete change JSON/CSV.

Available options

Finalization policy
Accept supported text revisions · Reject supported text revisions

Capabilities and limits

  • One30MiB unsigned/nonmacro/nonencrypted DOCX; ZIP≤80MiB expanded/10,000 entries, total XML20MiB/1,000,000 elements; each XML≤200,000 elements/depth128 and UTF8 XML1.0. Whole-package preflight runs before any output.
  • Only direct paragraph wrappers around ordinary text runs in main/header/footer/footnotes/endnotes stories. Complex field/property/paragraph-mark/table-cell/move/customXML/conflict or nested revisions, wrapper-local namespace bindings, nontext revised run objects and modern comments/people cause whole-package refusal. Ordinary unrevised parts retain bytes. Stopping tracking is not metadata anonymity or forensic erasure; no universal Word pagination claim.
Open Finalize DOCX text revisions and classic comments →

Tools used in this article

Filename-template MP3 tag editor →Persist composed MP3 titles, artists and track numbers from an explicit filename template while preserving MPEG and unrelated tag frames.CUE-index recording splitter →Split one WAV, MP3 or raw FLAC recording at explicit CUE indexes and export PCM16 WAV tracks with complete source-frame mappings.Finalize DOCX text revisions and classic comments →Accept or reject supported DOCX run-level text revisions, delete classic comment structures and stop future revision tracking.