Working on a PNG module.
Clone or download
Pull request Compare This branch is 515 commits behind openpreserve:integration.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


JSTOR/Harvard Object Validation Environment


Copyright 2003-2012 by JSTOR and the President and Fellows of Harvard College, 20015 - by the Open Preservation Foundation. JHOVE is made available under the GNU Lesser General Public License (LGPL).

Rev. 1.12.1, 2015-08-13

JHOVE Homepage


JHOVE (the JSTOR/Harvard Object Validation Environment, pronounced "jhove") is an extensible software framework for performing format identification, validation, and characterization of digital objects.

  • Format identification is the process of determining the format to which a digital object conforms: "I have a digital object; what format is it?"
  • Format validation is the process of determining the level of compliance of a digital object to the specification for its purported format: "I have an object purportedly of format F; is it?"
  • Format characterization is the process of determing the format-specific significant properties of an object of a given format: "I have an object of format F; what are its salient properties?"

These actions are frequently necessary during routine operation of digital repositories and for digital preservation activities.

The output from JHOVE is controlled by output handlers. JHOVE uses an extensible plug-in architecture; it can be configured at the time of its invocation to include whatever specific format modules and output handlers that are desired. The initial release of JHOVE includes modules for arbitrary byte streams, ASCII and UTF-8 encoded text, AIFF and WAVE audio, GIF, JPEG, JPEG 2000, TIFF, and PDF; and text and XML output handlers.

The JHOVE project is a collaboration of JSTOR and the Harvard University Library. Development of JHOVE was funded in part by the Andrew W. Mellon Foundation. JHOVE is made available under the GNU Lesser General Public License (LGPL; see the file LICENSE for details).

JHOVE is currently being maintained by the Open Preservation Foundation.

CD Status

  • Build Status Travis-CI: mvn install integration

  • Build Status OPF Jenkins: mvn verify integration

  • Build Status OPF Jenkins: mvn deploy integration

Version 1.12

The OPF is preparing to release a JHOVE 1.12.x-beta in September.

What's changed?

  • Support for Java 1.6 onwards only.
  • Maven build and packaging.
  • Simple cross platform installer.
  • Automated build, test, QA and deployment.
  • Automated test harness.

What's not changed?

The code, well as little as necessary. A small change was required to enable the Maven build to update the version and date details automatically. I've (@carlwilson) made a few "non-destructive" changes to the code, mainly using compiler/IDE guidance: removing unnecessary else's; and eliminating some obvious repetition.


  1. Java JRE 1.6 (JHOVE was originally implemented using the Sun J2SE SDK 1.4.1 and has been tested to work with 1.5). Version 1.12 of JHOVE is built and tested against Oracle JDK 7, and OpenJDK 6 & 7 on Travis. Relesases are built using Oracle JDK 7 from the OPF's Jenkins server.

  2. If you would like to build JHOVE from source, then life will be easiest if you use Apache Maven.

Getting JHOVE

For Users: JHOVE Cross Platform Installer

Download instructions coming in September 2015.

For Developers: JHOVE JARs via Maven

JHOVE is available through Maven, currently we're distributing through the OPF's Maven repository during development. The final 1.12 release artifacts will be published to Maven central. If you'd like to try the latest Maven modules then add:


to your project's POM file then use this dependency for the core classes (e.g. JhoveBase, Module, ModuleBase, etc.):


and this for the JHOVE core module implementations:


For Developers: Building JHOVE from source

Clone this project, checkout the integration branch and use Maven: e.g.:

git clone
cd jhove
git checkout integration
mvn clean install

Currently see the Project Structure section for a guide to the Maven artifacts produced by the build.


Application Installation

Download the JHOVE installer, this requires Java 1.6 or later to be pre-installed. We'll assume that you've downloaded <userHome>/Downloads/jhove-xplt-installer-1.12.x.jar, where x is the current revision/build number. Installation is OS dependant.


Currently only tested on Windows 7 Simply double click the downloaded installer JAR in Explorer. If Java is installed then the windowed installer will guide you through selection. It's best to stay with the default choices if installing the beta.

Once the installation is finished you'll be able to double click C:\Users\yourName\jhove-beta\jhove-gui to start the JHOVE GUI. Alternatively start a command window, e.g. winkey then type cmd, then issue these commands:

C:\Users\yourName>cd jhove-beta

to display the command line usage message.

Mac OS

Currently only tested on Mavericks Simply double click the downloaded installer JAR in Explorer. If Java is installed then the windowed installer will guide you through selection. It's best to stay with the default choices if installing the beta.

Once the installation is finished you'll be able to double click /Users/yourName/jhove-beta/jhove-gui to start the JHOVE GUI. Alternatively start a command window Terminal and then issue these commands:

cd ~/jhove-beta

to display the command line usage message.


Currently only tested on Ubuntu 14.10 Once the installer is downloaded start a terminal, e.g. ctrl+alt+T, and type the following, assuming the download is in ~/Downloads:

java -jar ~/Downloads/java-xplt-installer-1.12.x.jar

Once the installation is finished you'll be able to:

cd ~/jhove-beta

to run the command line application and show the usage message. Alternatively:

cd ~/jhove-beta

will run the GUI application.


We'ved moved to Maven and we've taken the opportunity to update the distribution. For now we're producing:

  • a Maven package for developers wishing to incorporate JHOVE in their own software;
  • a "fat" (1MB) jar that contains the old CLI and desktop GUI, for anyone who doesn't want to use the new installer;
  • a simple cross platform installer that installs the application jar, support scripts, etc.

Currently all options, including the installer require Java 1.6 or more recent to be pre-installed. Supporting 1.5 is no longer realistic, Oracle end of lived it's own 1.6 distribution in 2012. We've kept to 1.6 as a transition towards moving to 1.7, if you really need a 1.5 compatible build then you can override the target version for the Maven build, e.g.:

mvn clean install

This also produces an installer that will work on 1.5 JREs.


jhove [-c config] [-m module] [-h handler] [-e encoding] [-H handler]
           [-o output] [-x saxclass] [-t tempdir] [-b bufsize]
           [-l loglevel] [[-krs] dir-file-or-uri [...]]

-c config   Configuration file pathname
-m module   Module name
-h handler  Output handler name (defaults to TEXT)
-e encoding Character encoding used by output handler (defaults to UTF-8)
-H handler  About handler name
-o output   Output file pathname (defaults to standard output)
-x saxclass SAX parser class (defaults to J2SE default)
-t tempdir  Temporary directory in which to create temporary files
-b bufsize  Buffer size for buffered I/O (defaults to J2SE 1.4 default)
-l loglevel Logging level
-k          Calculate CRC32, MD5, and SHA-1 checksums
-r          Display raw data flags, not textual equivalents
-s          Format identification based on internal signatures only
dir-file-or-uri Directory or file pathname or URI of formated content

All named modules and output handlers must be found on the Java CLASSPATH at the time of invocation. The JHOVE driver script, jhove/jhove, automatically sets the CLASSPATH and invokes the Jhove main class:

jhove [-c config] [-m module] [-h handler] [-e encoding] [-H handler]
      [-o output] [-x saxclass] [-t tempdir] [-b bufsize] [-l loglevel]
      [[-krs] dir-file-or-uri [...]]

The following additional programs are available, primarily for testing and debugging purposes. They display a minimally processed, human-readable version of the contents of AIFF, GIF, JPEG, JPEG 2000, PDF, TIFF, and WAVE files:

java ADump  aiff-file
java GDump  gif-file
java JDump  jpeg-file
java J2Dump jpeg2000-file
java PDump  pdf-file
java TDump  tiff-file
java WDump  wave-file

For convenience, the following driver scripts are also available:

adump  aiff-file
gdump  gif-file
jdump  jpeg-file
j2dump jpeg2000-file
pdump  pdf-file
tdump  tiff-file
wdump  wave-file

The JHOVE Swing-based GUI interface can be invoked from a command shell from the jhove/bin sub-directory:

jhove-gui -c <configFile>

where is the pathname of the JHOVE configuration file.

Project Structure

A quick introduction to the restructured Maven project. The project's been broken into 3 Maven modules with an additional installer module added.


All Maven artifacts are are produced in versioned form, i.e. ${artifactId}-${project.version}.jar, where ${project.version} defaults to 1.12.0-SNAPSHOT unless you explicitly set the version number.


The jhove project root, acts as a Maven parent and reactor for the submodules. This simply builds sub-modules and doesn't produce any artifacts, but decides which sub-modules are built.

The jhove-core and jhove-modules are most likely all that are required for developers wishing to call and run JHOVE from their own code.


The jhove-core module contains all of the main data type definitions and the output handlers. This module produces a single JAR:


The jhove-core JAR contains a single module implementation, the default BytestreamModule. To the format specific modules you'll need the jhove-modules JAR.


The jhove-modules contains all of JHOVE's core format specific module implementations specifically:


These are all packaged in a single modules jar:



jhove-apps contains the command line and GUI application code and builds a fat jar containing the entire Java application. This JAR can be used to execute the command line app:


Finally the jhove-installer module takes the fat jar and creates a Java based installer for JHOVE. The installer bundles up invocation scripts and the like, installs them under <userHome>/jhove-beta/ (default, can be changed) while looking after:

  • variable substitution to ensure that JHOVE_HOME and the like are set to reflect a users install location;
  • making sure that Windows users get batch scripts, while Mac and linux users get bash scripts; and
  • optionally generate unattended install and uninstall files.

The module produces two JARs, one called jhove-installer-${project.version}, which contains the jars for the installer, and an executable JAR to install JHOVE:


The xplt stands for cross-platform.