---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Supported file types

# Supported file types for Autonomous Engineer {#ariaid-title1}

Release version: Brazil  
Updated September 23, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Autonomous Engineer accepts images, documents, code files, and file types specific to ServiceNow as uploads. Supported formats, size limits, and general guidelines apply when generating apps and metadata.

## File types {#ae-supported-file-types__section_file_types}

{#ae-supported-file-types__id_yrd_rs4_nkc__entry__2}

| Category | Extensions |
|-|-|
| Code and scripts | .js, .ts, .tsx, .jsx, .py, .java, .css, .html, .xml, .json |
| Documents | .txt, .md, .csv, .log |
| Images | .png, .jpg, .jpeg, .gif, .svg, .webp |
| Specific to ServiceNow | .now.ts (Fluent DSL), .xml (update sets) |
[Table 1. Supported file types]

{#ae-supported-file-types__id_yrd_rs4_nkc}

You can also use MCP server connections, such as for Figma, to provide context for Autonomous Engineer. For more information, see [MCP connections and Autonomous Engineer](https://www.servicenow.com/docs/XmPnpd62BMPtw2f97wqOww "MCP connections enable Autonomous Engineer to access external tools and resources through standardized communication, extending the planning and implementation workflow with data and context from third-party systems.").

## Size limits {#ae-supported-file-types__section_size_limits}

{#ae-supported-file-types__id_lt5_rs4_nkc__entry__2}

| Category | Description |
|-|-|
| Individual file | Up to 10 MB per attachment. |
| Images | View and analyze screenshots and diagrams directly in the chat. |
[Table 2. Size limits]

{#ae-supported-file-types__id_lt5_rs4_nkc}

## File upload guidelines {#ae-supported-file-types__section_tips}

* Upload text-based files to let Build Agent read and analyze the full content, then incorporate it into your app.
* Upload images or screenshots to provide UI mockups, error screenshots, or architecture diagrams as context for development.
* If an attachment is not visible after a window reload, re-upload the file.
{#ae-supported-file-types__ul_dfb_ss4_nkc}

## File uploads and your project {#ae-supported-file-types__section_file_uploads_and_project}

Uploaded files are available only within the current conversation and aren't added to your ServiceNow project or application automatically.
{#ae-supported-file-types__id_f3t_ss4_nkc__entry__2}

| Upload | What Build Agent can do |
|-|-|
| A script file (.js, .ts) | Read the file, then write the content into your app using the appropriate source file tool. |
| A screenshot of an error | Analyze the screenshot and help resolve the issue. |
| A CSV or data file | Use the data to inform table design or generate test data. |
| A mockup or diagram | Use the file as a reference to build a UI page. |
| An XML update set | Analyze the file and recreate the metadata using Fluent APIs. |
[Table 3. Upload scenarios]

{#ae-supported-file-types__id_f3t_ss4_nkc}  
Note:  
* Uploading a file does not add it to your app. To incorporate file content into your project, ask Build Agent to do so explicitly, for example, "Add this script to my app as a script include."
* Uploaded files don't persist across sessions. If the window reloads, re-upload the file for Build Agent to access the content again.
{#ae-supported-file-types__ul_jtq_b1g_mjc}