Content libraries are the objects for VM, vApp and other types of files such as ISO Images, text files, etc. these objects can be shared across vCenter Servers in the same or different locations.
A content library stores and manages content in the form of library items. A single library item can consist of one file or multiple files. For example, the OVF template is a set of files (.ovf, .vmdk, and .mf).
In previous versions of vSphere, content libraries supported only OVF templates. As a result, VM and vApp templates were both converted to OVF files when you uploaded them to a content library. Starting with vSphere 7.0 Update 1, content libraries also support VM templates. So, templates in the content library can either be of the OVF Template type, or the VM Template type. vApp templates are still converted to OVF files when you upload them to a content library. you can manage the content library either from single vCenter or different vCenter. through HTTPS (Secure connection)
Content library can be created under two types, local which store only single vCenter server instances. another is subscribed content library. under this library, you cannot upload and import items into a subscribe library. It is the administrator of the published library who manages the templates.
Steps to follow
Click on the Content library under vSphere client- and follow the below steps
Click on the Create option and enter the name and click on next button.
Select the appropriate option and click on next button.
(Optional) On the Apply security policy page, select Apply Security Policy and select OVF default policy.
Click Next.
On the Add storage page, select datastore as a storage location for the content library contents and click Next.
On the Ready to complete page,
review the details and click Finish.