Storing images in the database

Administrators and users with the image_admin or content_admin role can upload and store images in the database. These images are saved in the Images [db_image] table. Uploading an image to the database allows it to be referenced from HTML fields by appending the name of the image to the URL of the instance.

Note: The db_image table is a public table that does not have any security restrictions. Unauthenticated users have full access to images uploaded to the db_image table.

Images vs attachments

If you want to access an image from a record, or if you want to prevent users from appending the image name to the URL of the instance, upload it as an attachment instead. When you upload an image as an attachment, the image is saved in the Attachments [sys_attachment] table. See Administer attachments and Add and manage attachments for more information.

Acceptable image file types

Upload image files with the following extensions:

• .gif
• .jpg
• .png
• .bmp

Note: The system does not support uploading zip files that contain .bmp images.

If you upload an image that may not be supported in Internet Explorer browsers, a warning message appears.

The system does not support uploading images in the .ico format through this interface. Microsoft Internet Explorer requires the .ico format for favorite icons. To upload an .ico image, attach the .ico image to a record instead of using the standard image upload interface.

To understand how to insert an image into a form record, see the Insert an image into your article, incident, or other form record blog post in the ServiceNow Community.

• Update an existing image
  You can change an existing image to an updated version.
• Upload one or more images
  You can upload one image or multiple images at one time.
• Restrict file extensions
  Use the glide.ui.strict_content_types to restrict the image file extensions that appear in the UI.

Parent Topic:User interface configuration