Cover artwork
Artwork support varies by container, tag standard and player. Resize an unnecessarily large image before embedding and verify it in the intended player.
1. Select media file
Drop a video here
or click to browse
Supported formats: MP4, MOV, MKV, MP3, M4A, AAC, FLAC
Maximum file size: 2 GB
2. Edit metadata
0 / 500
Store the selected image inside the output file when the target container supports it.
4. Preview and export
Media preview
No videos have been added yet.
Format
—
Resolution
—
Duration
—
File size
—
Output file
Output file
Result preview
Apply metadata to enable download.
Original file
—
Updated file
—
Difference
—
Format
—
If the implementation writes files in the browser, local media need not be uploaded to AppKiro. However, parsing and rewriting still use browser memory. A remote URL flow uses the network and may be read-only depending on CORS, range and write architecture.
What does a media metadata editor change?
It updates supported descriptive fields such as title, artist, album, year, description or cover art inside the file container. It does not change visible pixels or spoken audio unless the implementation performs a separate media encode.
Metadata describes a file; it is not the visible content
Media metadata stores descriptive and technical information in a container or tag structure. Editing a title, artist or cover image does not replace text already shown in video frames, remove a watermark or change the actual audio recording.
Who uses a metadata editor?
Music and video libraries, archivists, podcasters, photographers, CMS teams and developers use metadata editing to improve titles, attribution, grouping, cover artwork and searchability in compatible players and asset systems.
Useful metadata editing tasks
- Correct a title, artist or album name before delivery.
- Add a description, copyright notice or project identifier.
- Embed cover artwork for an audio file or supported video container.
- Standardize year, genre, track and collection fields across a library.
How to edit media metadata
Choose a compatible video or audio file and let the parser display existing fields.
Edit only the descriptive values you intend to change; leave other fields unchanged.
Add, replace or remove cover artwork only when the current container writer supports it.
Compare Before and After, including fields that will be cleared or overwritten.
Write a separate output file, re-open it with Metadata Extraction and keep the original until verification is complete.
Important metadata controls
Advanced fields
Expose only fields the writer can preserve and serialize correctly. A generic UI must not imply that every container supports every tag.
No re-encoding
Changing container tags can often avoid decoding video or audio streams, but this is an implementation fact. Claim “no re-encode” only after checking the actual writer path.
Technical versus descriptive metadata
Title and artist are descriptive. Codec, duration and resolution are normally derived from media streams and should not be presented as freely editable tags.
Editing and extracting metadata are different workflows
Metadata Extraction reads and reports what a file contains. Metadata Editor attempts to modify supported writable fields and creates a new file. Link the two pages as inspect → edit → verify rather than targeting the same intent.
How metadata edits are handled
If the implementation writes files in the browser, local media need not be uploaded to AppKiro. However, parsing and rewriting still use browser memory. A remote URL flow uses the network and may be read-only depending on CORS, range and write architecture.
Metadata editing limitations
- Players and asset systems may ignore, rename or prioritize tags differently.
- Not every field is writable in every container, and some values may be stored in container-specific structures.
- Technical stream properties cannot be changed by editing descriptive tags.
- Large files can still require significant memory even when media streams are copied rather than re-encoded.
Common metadata problems
The player does not show the new title
The player may cache data, read a different tag namespace or ignore that field. Re-open the file and compare with extraction output.
Cover art is missing
The target container, tag type or player may not support embedded artwork. Check the output structure and use a compatible image.
The output is almost the same size
Metadata is usually small relative to media streams. Similar size is expected and does not prove whether re-encoding occurred.
Some fields disappeared
The writer may not preserve unknown tags. Source code should retain unsupported fields where possible, and the UI must warn before destructive rewriting.
Media metadata editor FAQ
What metadata can I edit?
Only fields supported by the current parser, writer and container. Common examples are title, artist, album, year, description, genre, comment, copyright and cover art.
Does metadata editing change the video picture or audio?
Not when the implementation rewrites tags or container fields while copying media streams. Verify the actual path before promising no re-encode.
Can I change resolution or codec as metadata?
No. Resolution and codec describe the actual media streams. Use a converter or resizer to change them.
Can I add cover art to a video?
Only if the target container and current writer support embedded artwork. Support in players also varies.
Will every player show the same tags?
No. Players use different tag standards, mappings and priorities. Test the output in the intended destination.
Can I remove metadata?
Supported fields can be explicitly cleared when the writer implements deletion. Do not interpret an empty input as consent to erase data.
Is the original file changed?
No. The safer workflow creates a separate output and keeps the original until the tags are verified.
Are local files uploaded?
Only claim browser-local editing when confirmed in source code. URL-based input still requires access to the remote host.
Why can I read a field but not edit it?
A parser may expose more fields than the writer can safely serialize. Read support and write support are separate capabilities.
How do I verify the result?
Open the exported file in Metadata Extraction and in the target player or asset system. Compare the changed fields and artwork before replacing the source.
Related metadata and media tools
Metadata ExtractionInspect existing tags, tracks and technical properties before and after editing.Video ConverterChange actual codec or container when metadata editing is not enough.Video Thumbnail GeneratorCreate a separate poster or preview image from video frames.Video WatermarkAdd visible ownership identification instead of hidden metadata.