The Java™ Platform, Standard Edition Runtime Environment (JRE) is intended for software developers and vendors to use with their applications.
The Java SE Runtime Environment contains the Java virtual machine, runtime class libraries, and Java application launcher that are necessary to run programs written in the Java programming language. It is not a development environment and does not contain development tools such as compilers or debuggers. For development tools, see the Java SE Development Kit (JDK™).
When you deploy an application written in the Java programming language, your software bundle will probably consist of the following parts:
You already have the first part, of course. The remainder of this document covers the other two parts. Also see the Developers website:
To run your Java 8 application, a user needs the Java SE 8 Runtime Environment, which is available from Oracle under the Oracle Technology Network License Agreement for Oracle Java SE, which is free for personal use, development, testing, prototyping and some other important use cases covered in this FAQ. Or, you can redistribute the Java SE 8 Runtime Environment via an ISV agreement with Oracle (Contact Oracle Sales for more information).
The final step in the deployment process occurs when the software is installed on an individual user's system. Installation consists of copying software onto the user's system, then configuring the user's system to support that software. You should ensure that your installation procedure does not overwrite existing JRE installations, as they may be required by other applications.
NOTE - The license for this software does not allow the redistribution of beta and other pre-release versions.
Current releases of the Oracle Java SE 8 Runtime Environment require a commercial license for redistribution. Legacy releases were licensed differently. Please see this FAQ for more information.
The files that make up the Java SE Runtime Environment are divided into two categories: required and optional. Optional files may be excluded from redistributions of the Java SE Runtime Environment at the vendor's discretion.
The following section contains a list of the files and directories that may optionally be omitted from redistributions with the Java SE Runtime Environment. All files not in these lists of optional files must be included in redistributions of the runtime environment.
The following files may be optionally excluded from redistributions. These files are located in the jre1.8.0_<version> directory, where <version> is the update version number. Solaris and Linux filenames and separators are shown. Windows executables have the ".exe" suffix. Corresponding files with
_g in the name can also be excluded.
The corresponding man pages should be excluded for any excluded executables (with paths listed below beginning with bin/, for the Solaris™ Operating System and Linux).
lib/ext/ [Everything under this directory can be excluded]
sunjce_provider.jar,sunec.jar, sunpkcs11.jar and sunmscapi.jar -
JCA/JCE providers for Java Cryptography APIs. Some providers are
not available on all OS or Architectures. The runtime environment
must contain at least one implementation of each of the required
Security algorithms as described in:
localedata.jar - contains many of the resources needed for
non US English locales
dnsns.jar - for the InetAddress wrapper of
JNDI DNS provider
bin/rmid - [.exe, and .dll on Microsoft Windows] Java RMI Activation
bin/rmiregistry - Java Remote Object Registry
bin/tnameserv - Java IDL Name Server
bin/keytool - Key and Certificate Management Tool
bin/kinit - [Microsoft Windows] Used to obtain and cache Kerberos
bin/klist - [Microsoft Windows] Kerberos display entries in
credentials cache and keytab
bin/ktab - [Microsoft Windows] Kerberos key table manager
bin/policytool - Policy File Creation and Management Tool
bin/orbd - Object Request Broker Daemon
bin/servertool - Java IDL Server Tool
lib/javaws.jar - Java Web Start
lib/jfr.jar - Flight Recorder Files
When redistributing the JRE on Microsoft Windows as a private application runtime (not accessible by other applications) with a custom launcher, the following files are also optional. These are libraries and executables that are used for Java support in Internet Explorer and Mozilla family browsers; these files are not needed in a private JRE redistribution.
All JavaFX related files:
[As long as you don't include any other JavaFX related files]
- JavaFX third-party license information
lib/ant-javafx.jar - JavaFX packager ant tasks
lib/javafx.properties - JavaFX properties file
JavaFX native libraries [Microsoft Windows]:
JavaFX native libraries [Mac OS X]:
JavaFX native libraries [Linux-i586]:
JavaFX native libraries [Linux-x64]:
The limited set of files from the Java SE Development Kit (JDK) listed below may be included in vendor redistributions of the Java SE Runtime Environment. All paths are relative to the top-level directory of the JDK. The corresponding man pages should be included for any included executables (with paths listed below beginning with bin/ , for the Solaris™ Operating System and Linux).
lib/cmm/PYCC.pf Color profile; This file is required only if one
wishes to convert between the PYCC color space
and another color space.
All .ttf font files in the lib/fonts directory
Note that the LucidaSansRegular.ttf font is already
contained in the Java SE Runtime Environment, so
there is no need to bring that file over from the JDK.
The javac bytecode compiler, consisting of the following files:
bin/javac [Solaris™ Operating System, Linux and OS X]
bin/sparcv9/javac [Solaris Operating System (SPARC(R) Platform Edition)]
bin/amd64/javac [Solaris Operating System (AMD)]
bin\javac.exe [Microsoft Windows]
lib/tools.jar [All platforms]
lib/jconsole.jar The Jconsole application.
bin\server\ On Microsoft Windows platforms, the JDK includes both
the Java HotSpot™ Server VM and Java HotSpot
Client VM. However, the Java SE Runtime Environment
for Microsoft Windows platforms includes only the
Java HotSpot Client VM. Those wishing to use the
Java HotSpot Server VM with the Java SE Runtime
Environment may copy the JDK's jre\bin\server folder
to a bin\server directory in the Java SE Runtime
Environment. Software vendors may redistribute the
Java HotSpot Server VM with their redistributions of
the Java SE Runtime Environment.
Due to import control restrictions for some countries, the Java Cryptography Extension (JCE) policy files shipped with the Java SE Development Kit and the Java SE Runtime Environment allow strong but limited cryptography to be used. These files are located at:
where <java-home> is the jre directory of the JDK or the top-level directory of the Java SE Runtime Environment.
An unlimited strength version of these files indicating no restrictions on cryptographic strengths is available on the JDK web site for those living in eligible countries. Those living in eligible countries may download the unlimited strength version and replace the strong cryptography jar files with the unlimited strength files.
<java-home>/lib/ directory as per the Java Platform, Standard Edition (Java SE) Documentation, including selecting one or creating your own Java Cryptography Extension policy file under
<java-home>/lib/security/policy. Once you select or create your own you are not required to include alternative policy files.
Root CA certificates may be added to or removed from the Java SE certificate file located at:
For more information, see "The cacerts Certificates File" section in the keytool documentation at:
From time to time it is necessary to update the Java platform in order to incorporate newer versions of standards that are created outside of the Java Community ProcessSM (JCPSM http://www.jcp.org/) (Endorsed Standards), or in order to update the version of a technology included in the platform to correspond to a later standalone version of that technology (Standalone Technologies).
The Endorsed Standards Override Mechanism provides a means whereby later versions of classes and interfaces that implement Endorsed Standards or Standalone Technologies may be incorporated into the Java Platform.
For more information on the Endorsed Standards Override Mechanism, including the list of platform packages that it may be used to override, see: