---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Attachment

# Attachment limit properties {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Attachment limit properties

ServiceNow controls email attachment limits through configurable system properties that govern both inbound and outbound emails.
These properties help manage the number and total size of attachments to prevent performance issues and ensure efficient email processing.
Show full answer Show less  

## Key Features

* **Inbound Email Attachment Limits:**
  * `glide.email.inbound.maxattachmentcount`: Maximum number of attachments per inbound email (default 30).
  * `glide.email.inbound.maxtotalattachmentsizebytes`: Maximum total size of attachments per inbound email in bytes (default 18,874,368 bytes, approx. 18 MB).
  * Attachments exceeding these limits are discarded, and a record with discard reason is saved in the `Email Attachments [sysemailattachment]` table.
  * Discarded attachments trigger the event `inbound.emailattachments.discarded`, which can be used to notify senders.
  * Duplicate attachments are prevented from attaching to the target record.
* **Outbound Email Attachment Limits:**
  * `glide.email.outbound.maxattachmentcount`: Maximum number of attachments per outbound email (default 30).
  * `glide.email.outbound.maxtotalattachmentsizebytes`: Maximum total size of attachments per outbound email in bytes (default 18,874,368 bytes).
  * Emails exceeding these limits are sent with attachments up to the maximum allowed; excess attachments are omitted and a warning is logged.
  * Because email encoding increases size, outbound size limits should be set below the maximum email size.
* **General Attachment Size Limit:**
  * `com.glide.attachment.maxsize` enforces the maximum size for any single attachment in the system and overrides larger values set by inbound and outbound email size properties.
* **Special Cases:**
  * Notifications including attachments exclude excess attachments beyond outbound limits and log warnings.
  * Scheduled reports sent by email without attachments if report size exceeds limits; recommended to send report links instead.
  * Exported record lists emailed as attachments respect outbound limits; if exceeded, attachments are omitted and warnings logged.

## Key Outcomes

* Efficient management of email attachment volume and size to maintain system performance and reliability.
* Visibility and traceability of discarded inbound attachments via logging and events, enabling proactive notification to email senders.
* Prevention of outbound email failures or oversized emails by enforcing limits and logging warnings for corrective action.
* Clear understanding for ServiceNow administrators on how to configure these properties to balance attachment needs with system performance constraints.  
Several properties control email attachment limits.
To see the status of all email attachments, go to the Email Attachments \[sys_email_attachment\] table.

## Properties

All the properties are located in the System Property \[sys_properties\] table. Setting any
of the following properties to an excessively large value may cause performance issues.  
{#r_AttachmentLimitProperties__table_lft_wmt_gr__entry__2}

| Name | Description |
|-|-|
| glide.email.inbound.max_attachment_count | Sets the maximum number of attachments allowed per inbound email. * Type: integer * Default value: 30 * Learn more: Inbound Email Attachment Processing {#r_AttachmentLimitProperties__ul_vzt_jnt_gr} |
| glide.email.inbound.max_total_attachment_size_bytes | Sets the maximum total attachment size in bytes allowed per inbound email. * Type: integer * Default value: 18874368 * Learn more: Inbound Email Attachment Processing {#r_AttachmentLimitProperties__ul_bkz_nnt_gr} |
| glide.email.outbound.max_attachment_count | Sets the maximum number of attachments allowed per outbound email. * Type: integer * Default value: 30 * Learn more: Outbound Email Attachment Processing {#r_AttachmentLimitProperties__ul_uzh_4nt_gr} |
| glide.email.outbound.max_total_attachment_size_bytes | Sets the maximum total attachment size in bytes allowed per outbound email. To send an email, the system must encode the contents of the email. This process may significantly increase the size of the email, including any attachments. It is best to set this property to a value well below the maximum email size. * Type: integer * Default value: 18874368 * Learn more: Outbound Email Attachment Processing {#r_AttachmentLimitProperties__ul_obp_4nt_gr} |
[Table 1. Attachment limit properties]

{#r_AttachmentLimitProperties__table_lft_wmt_gr}  
Note:  
A different property, com.glide.attachment.max_size, sets the maximum file size allowed for any attachment in the system and overrides any larger values of glide.email.inbound.max_total_attachment_size_bytes and glide.email.outbound.max_total_attachment_size_bytes.

## Inbound email attachment processing

For inbound emails, the system enforces the maximum number and size of attachments as set
by the glide.email.inbound.max_attachment_count and
glide.email.inbound.max_total_attachment_size_bytes properties. When
an attachment for an inbound email exceeds either value, the attachment is discarded. A record is created in the Email Attachments \[sys_email_attachment\] table containing the discarded file name and the reason it was discarded. The discarded file remains in the Email \[sys_email\] record. The order in which the system processes the attachments determines which attachments are
discarded. This order may not be consistent from email to email.

When an inbound email attachment is discarded, the system also fires the
inbound.email_attachments.discarded event. You can use the event to
trigger a notification that alerts the email sender. For an example of a notification that
can be triggered by the event, see the inactive "Demo Email Attachment(s) Discarded"
notification.

Inbound email attachments are prevented from attaching to the target record if an identical
attachment exists.

## Outbound email attachment processing

For outbound emails, the system enforces the maximum number and size of attachments as set
by the glide.email.outbound.max_attachment_count and
glide.email.outbound.max_total_attachment_size_bytes properties.
Email records are created from various sources and may exceed the configured attachment
limits.

Emails that are ready to be sent from the Email \[sys_email\] table are subject to the
outbound attachment limits. Emails that exceed either limit trigger a warning in the email
system log and are sent with attachments up to the maximum number or total file size.

The log message for such an email might look like this: Maximum combined attachment size exceeded. (max:15728640 bytes). One or more attachment records ignored.

## Emails for notifications, scheduled reports, and exported tables

Notifications can be set to include all the attachments from the record that triggers the
notification. If the attachments exceed either of the outbound email attachment limits, the
system excludes the excess attachments from the email and logs a warning message.

Reports can be scheduled for email distribution as attachments. Large reports may exceed
the outbound attachment size limit. In this case, the system sends the scheduled report
email without the report attached and logs a warning message. To avoid the issue, send links
to large reports instead of sending the reports as attachments.

If a user attempts to export numerous records from a list that exceeds a configured warning
threshold, a dialog box offers the option to email the exported records as an attachment. If
the attachment exceeds the outbound attachment size limit, the system sends the email
without the exported record list attached and logs a warning message.

