Files and Text

Use Files on the create page or in the editor to give the agent material to reference while building or use inside your app. Upload files or paste text, then tell the agent what you want to create.

Two ways to use files

Reference material helps the agent understand what to build. A screenshot can guide the layout. A textbook chapter or pasted lesson notes can provide the subject matter for a learning app. The agent can use these sources to create the design, lessons, or questions without making the app display or fetch the original file.

Files used inside the app provide real media or data: a logo in the header, background music in a game, a 3D character, or a CSV that powers a catalog. The agent can use the saved file's URL in the app.

Both belong in Files. You do not need to choose a category. Describe your intent in How should the agent use this? (optional) or in your Build prompt. Adding a file makes it available to the agent; it does not automatically add it to the app's interface.

Examples

Recreate a design from a screenshot

Upload the screenshot and name it "Dashboard reference".

Example instruction: "Match the layout in this screenshot."

The agent uses the image to guide the interface. The screenshot itself does not need to appear in the app.

Turn a chapter into a study app

Paste a textbook chapter as text or upload a .txt file, and name it "Biology chapter 3".

Example instruction: "Create practice questions from this chapter."

In Build, you can ask for flashcards, explanations, and a quiz based on that material. The source guides the generated content; the app does not need to fetch or show the original chapter.

Use your logo in the app

Upload a PNG or SVG logo and name it "Company logo".

Example instruction: "Use this image as my app's logo."

You can specify placement in Build: "Use Company logo in the header. Keep it uncropped."

Build with real data and media

CSV or JSON: "Load Product catalog CSV and make a searchable catalog with name, price, and category."
Text: "Use Coach instructions as the system prompt for the chat assistant."
Audio: "Play Forest ambience as looping background music on the home screen."
3D model: "Use Player character GLB as the hero character in the 3D scene."
Images: "Use Mountain landscape as the onboarding background."

Before the first build

On the create page, write your prompt and select the + button (Add files) in the composer. Upload files or paste text using the same review flow as the editor. Review the details, then choose Add files to prepare them for creation.

Ready files appear alongside your prompt. Select a file to edit its details, or remove it before building. Finish adding any files still being reviewed, or discard the unfinished files, before you build.

When you build, your app is created first and the prepared files are saved to it. Generation starts after those save attempts finish. File saving is best effort: successful files are kept, and any files that fail are omitted. You continue to the editor automatically.

Prepared selections stay in this page's memory until submission. Refreshing or leaving before submission clears them, so keep the page open while preparing your app.

Explore built-in capabilities and example prompts in What can your app do? below the form.

Add files or text

Select + (Add files) in the editor composer, or open the Files tab and choose Add. Both open the same dialog and keep any unfinished review.
Choose an input. Files is selected by default.
- Files: Drag files in or choose files to upload.
- Text: Paste notes, instructions, or reference material and choose Add text.
Review the title and description. Optionally fill in How should the agent use this? to explain your intent.
Choose Save all. Files are saved together, and successful files appear in the Files tab. If any fail, they remain in the dialog for you to retry or remove. Only saved files are available to the agent.
Mention the file by its title in your Build prompt and describe what you want to create or change.

Pasted text is saved as a text file. It is a saved copy, so paste again when the source changes.

Pasting a URL into Build chat does not add its contents. If your request depends on the source, the agent first looks for a matching saved file and reads it when possible. If the content is missing, paste the relevant text or upload a file. If you already saved the source, mention its title or saved file URL so the agent can reuse it.

When you only want a supported embed, such as a YouTube player, the URL is enough. A URL shown as a link or copyable text also does not need a file. Creating a lesson from a video's contents requires the transcript or other source text, which you can paste or upload.

You can open a saved file to edit its details or copy its URL. Files stay available across Build turns.

Supported file types

Each file can be up to 10 MB. An app can hold up to 50 files and 100 MB in total.

Images: PNG, JPEG, GIF, WebP, SVG, and AVIF.
Audio: MP3 and WAV.
3D models: GLB (glTF Binary). Export from Blender with File → Export → glTF 2.0, choose Format: glTF Binary (.glb), and embed textures. Draco compression is not supported.
Text: .txt files, including pasted text.
JSON: .json files.
CSV: .csv files.

The builder can inspect supported image previews and read text, JSON, CSV, and SVG source content when needed. It cannot inspect audio or 3D model sources, so describe their contents and intended use. It can still use those files inside the app.

Tips for better results

Give files descriptive titles so you can refer to them clearly in Build.
Use the description for what the file contains and the optional usage field for what the agent should do with it.
Say whether an image is a design reference or an image to display when the intent could be unclear.
Review pasted text before saving, especially when you need a specific chapter or section.
For data files, describe the structure, such as "Array of objects with fields: name, price, category."
For audio and 3D models, describe the sound or model and its role in the app.
Deleting a file removes it as a source for future builds and removes its URL permanently. Parts of your app that use the URL may stop working.

For uploads from people using your published app, see File upload.