With upcoming changes to data protection and privacy laws in Europe coming into effect soon, we thought this would be a good time to remind everyone that we do have a privacy policy.
This applies to all users and visitors world-wide.

We have made a few changes to the language to make it clearer in relation to this new regulation but fundamentally, the terms and your rights are unchanged.

If you have any questions about this, please feel free to ask in the General Forum

How to stop meta data?

HandBrake for Windows support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
Alice00
Posts: 2
Joined: Fri Jun 08, 2018 10:35 pm

How to stop meta data?

Post by Alice00 » Fri Jun 08, 2018 10:39 pm

Description of problem or question:
Please can someone tell me how to stop handbrake from adding metadata to my mp4s? I want to stop it adding Owner and Computer metadata.



Steps to reproduce the problem (If Applicable):




HandBrake version (e.g., 1.0.0):




Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):


Windows 10

HandBrake Activity Log ***required*** (see How-to get an activity log)

Code: Select all

Please replace this text with the contents of your log file between the two code tags - OR -  provide a pastebin URL in place of these 3 lines.

User avatar
s55
HandBrake Team
Posts: 9071
Joined: Sun Dec 24, 2006 1:05 pm

Re: How to stop meta data?

Post by s55 » Fri Jun 08, 2018 10:48 pm

What do you mean by "Owner and Computer metadata."?

Edit: Ah, you mean the file metadata, not container metadata.

That's Windows that does this, not HandBrake. As far as I know there is no way to prevent it.
That's why most your files will have this, regardless of whether they came from HandBrake or not.

Alice00
Posts: 2
Joined: Fri Jun 08, 2018 10:35 pm

Re: How to stop meta data?

Post by Alice00 » Sun Jun 10, 2018 5:43 pm

Oh yes, it was Windows metadata. :oops:

Post Reply