If this site goes down it is because of the crappy DreamHost web hosting: They will disable your "unlimited traffic" web server if a single bot hammers the site with a moderate load.  If necessary, an alternate ExifTool forum page is available at

Main Menu

Any performance impacts of using -api LargeFileSupport=1?

Started by RhetTbull, June 29, 2022, 01:40:57 AM

Previous topic - Next topic


I am the author/maintainer of the tool which exports photos with associated metadata from Apple Photos.  osxphotos will optionally use exiftool to write metadata to the exported files or read metadata from files to use in it's template system ( for naming exported files.  A user recently pointed out that this fails if the file is > 4GB (which is rare but can happen for video files).  osxphotos calls exiftool from a custom python interface I created for this purpose (maintains a singleton exiftool subprocess for better performance).  The easiest fix for this issue appears to be including -api largefilesupport=1 in the parameters to exiftool.  Is there any performance impact of leaving this enabled all the time?  If so, I may want to check the file size of the photo/video in question and only enable this when needed.


* Did you read FAQ #3 and use the command listed there?
* Please use the Code button for exiftool code/output.
* Please include your OS, Exiftool version, and type of file you're processing (MP4, JPG, etc).


Perfect -- thanks! The tool in question runs only on macOS which appears to support large files in exiftool so I don't see any reason from that thread to not enable this by default.