#Video metadata editor in windows 10 zip file

Case B: rename exiftool(-k).exe to exiftool.exe (=keep exe extension!).

Case A: rename exiftool(-k) to exiftool (=don't add exe extension!).

What you need to do (depending on the case above), is: How come there can be Case A or B? Because it depends on your Windows settings. After unzipping, you will see:Ĭase A: exiftool(-k) or Case B: exiftool(-k).exe

#Video metadata editor in windows 10 zip file

You only need to download 'Windows Executable' zip file from here. However, because GUI is developed in Win7 environment, I can't guarantee backward compatibility. Obviously, such data won't be displayed correctly in GUI Metadata panel, because here, UTF-8 encoded data is expected.ĮxiftoolGUI should run on WinXP up to Win7-64bit. If really needed, then you can still enter 'old' ANSI (non-UTF-8) encoded data by using -L option in ExifTool direct mode, i.e: Anyway, all this concerns only 'foreign' characters: if you allready used 'standard' alphabet (ASCII) characters only, then you won't notice any difference. change/overwrite such tag content (which becomes UTF-8 encoded).īut be aware, that UTF-8 encoded Exif content might not be properly recognized by some other software. If you notice this, then this means, metadata content isn't UTF-8 encoded. It can/will happen, that GUI will show some 'weird' characters where country specific characters should appear -if at all, this can/will happen for existing Exif metadata content (i.e: Exif:Artist). However, Metadata Working Group (MWG) organisation recommends using UTF-8 in Exif as well. Right now, the only exception is Exif, which oficially doesn't support UTF-8 yet. For Iptc metadata, UTF-8 charset has also become officially recommended. It's about displaying 'foreign', country specific characters:įor Xmp metadata, UTF-8 charset is used as default charset since beginning, so nothing changes here. edited metadata values will be automatically saved in UTF-8 format.characters inside metadata will be shown properly, if metadata content is UTF-8 encoded.-batch capability (where appropriate), means: you can select multiple files and modify them at once.īasic idea behind GUI is, to keep it simple! Thus, only those options are implemented, which I believe, are essential for majority of users.įor ALL metadata, UTF-8 character set encoding/decoding is used.-ability to edit most frequently used metadata tags,.-view all metadata that ExifTool recognizes,.When making ExifToolGUI, the main goal was: There are already some GUI's that make use of ExifTool, but some of them are not flexible enough (for my needs) and/or have somehow limited use. So, I've decided to make some simple ExifTool GUI for my private use. Such approach gives ExifTool great flexibility, but is somehow difficult to use -especially for those, who don't use ExifTool regulary. That means, there's no Graphic User Interface (GUI), so all work must be done by typing commands inside 'Command Prompt' window. The only downside for many potential users is the fact, that ExifTool is a 'command-line' utility. -it is very secure to use, is regulary updated and has the best possible support.

-it allows to edit almost any metadata tag,.

-it shows more metadata tags than any other tool,.

In my opinion, ExifTool by Phil Harvey, is the best I've found so far.

There are many tools for viewing/editing metadata inside image files.