--- title: "Content Store" slug: "content-store" description: "Store images, files, and HTML content in the Mapp Engage Content Store: file types, size limits, expiration, placeholders, and permissions." status: "update" updated: 2026-10-21T12:18:54Z published: 2026-10-21T12:18:54Z canonical: "docs.mapp.com/content-store" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Content Store The Content Store is the central library for files and HTML content in Mapp Engage. You store an image, a document, or an HTML snippet once and use it in emails and landing pages. Each item in the Content Store is called a content store element. --- ## What You Can Store You can upload files or create HTML content directly in the Content Store. Mapp Engage sorts each element into a tab based on its file type (MIME type). | Tab | Contains | | --- | --- | | **Images** | Image files, for example JPEG, PNG, and GIF | | **Text** | Text-based files and HTML content, for example HTML, CSV, XML, and plain text | | **Media** | Video and audio files | | **Other** | All other file types, for example PDF | | **All Files** | All elements | Mapp Engage does not accept files that can contain executable or malicious code, for example `.exe` or `.lnk` files. Every upload is scanned for viruses. If an image is rejected because of suspicious content, see [Why does uploading an image to Content Store fail with XSS error due to suspicious content?](/v1/docs/uploading-image-to-content-store-fails-with-xss-error-due-to-suspicious-content) --- ## File Size - By default, you can upload images of up to 1 MB. Mapp Engage removes unnecessary metadata from uploaded images. - If you need a higher limit, contact your account manager. The limit can be raised in steps of 1 MB up to 4 MB. The request needs approval from engineering. - For emails, keep images small. The recommended size is 100 KB per image. Large images and attachments hurt deliverability and increase data costs for contacts on mobile networks. - Use 72 dpi for images that recipients view on screen and 300 dpi for images that recipients print. --- ## Add Elements to the Content Store ### Create an Element 1. Go to *Content > Content Store* and click **Create**. 2. Enter a **Name**. 3. Optional: Enter a **Description**. For images, the description is used as ALT text when you insert the image into a message. 4. Under **Content / Attachment**, select **Upload File** and click **Browse** to select a file. To create HTML content instead, select **HTML / HTML Editor**. 5. Optional: Set an **Expiration Date**. See *Expiration* below. 6. Click **Save**. For all fields, see [Compose Content Store Element](/v1/docs/create-new-content-element-window). ### Images Stored Automatically Images can also get into the Content Store without a manual upload: - **HTML emails:** If an HTML email references images that are not yet in the Content Store, Mapp Engage can ask you to upload them in the **Upload Missing Images** window. The uploaded images are stored as content store elements. The element name is taken from the image name in the HTML code. For the image handling options, see [Add and Configure Images in HTML Emails](/v1/docs/insert-images-in-an-email). - **CMS emails:** Images that you upload in a paragraph of a CMS email are saved to the Content Store and can be reused in other messages. --- ## Use Elements in Messages and Landing Pages Each element has an ID and two placeholders. To see them, click the element in the Content Store. The **Details** section opens below the list. | Placeholder | Inserts | | --- | --- | | `<%InsertCSE id="1234"%>` | The element itself | | `<%InsertCSELink id="1234"%>` | A link to the element | The Details section lists the placeholders for emails under **Placeholder for Email** and for landing pages under **Placeholder for Website**. Both use the same format. For the steps, see [Use a Content Store Element in an Email](/v1/docs/use-a-content-element-in-an-email). To attach a file from the Content Store to an HTML email, see [Add Attachments to an HTML Email](/v1/docs/add-an-attachment-to-a-message). --- ## Expiration - By default, an element is deleted 180 days after it was last used. Each use restarts the 180 days, for example when a recipient opens an email that loads the image. - If you turn off **Automatic Expiration Date** and set a date, the element is deleted on that date, even if it is still in use. > [!WARNING] > Warning > > When an element is deleted, emails that were already sent show a broken image instead. See [Image Missing After Sendout Due to Expired Content Store Element](/v1/docs/request-replacement-of-missing-or-expired-images). --- ## Categories Use content element categories to group related elements, for example all images of a campaign. An element can belong to several categories. See [Organize Content Store Elements with Categories](/v1/docs/organize-content-store-elements-with-categories). --- ## Permissions | Permission | Allows | | --- | --- | | 245 CMS: Edit own content store elements | View and edit your own elements | | 246 CMS: View all content store elements | View all elements in the system | | 244 CMS: Edit all content store elements | Edit all elements in the system | | 311 System Administration: View categories | View all categories, including content element categories | | 310 System Administration: Create and edit categories | Create and edit all categories, including content element categories | If **Visible to Everyone** is set to **No** for an element, access to it depends on these permissions. For all permissions, see [Global Permissions List](/v1/docs/global-permissions). --- ## Related Topics Reference for the Content Store screens: - [Content Store](/v1/docs/content-store-window) - [Compose Content Store Element](/v1/docs/create-new-content-element-window) - [Content Store Element Settings](/v1/docs/content-element-settings-window) - [Preview Content Store Element](/v1/docs/content-store-preview-window) - [Content Store Element Comments](/v1/docs/add-content-element-comment-window) - [Content Element Category: Overview](/v1/docs/content-element-category-overview-window)