Overview
Attach a PDF, image, or supported SPICE model file for a specific task. Name what you want read: the exact part, page, figure, label, or model declaration.
An attachment is not an instruction to change CAD. Select Ask for analysis, Agent for an intended edit, or Plan to review an approach first.
Supported File Types
In compatible builds, the shared chat picker accepts:
- PDF:
.pdf. - Images:
.png,.jpg,.jpeg,.gif, and.webp. - SPICE model text:
.lib,.sub,.cir,.mod,.prm,.txt,.inc,.spi,.sp,.ckt,.spice, and.mdl. - SPICE model archive:
.zip. - Size: up to 10 MiB per file.
Text and ZIP acceptance supports model-file workflows; it is not a generic archive importer or proof that the file contains valid SPICE. Direct .md, .csv, spreadsheet, audio, video, and host CAD-file attachments are not accepted by this picker. Use Artifacts for supported reusable text and BOM workflows, or paste a short relevant excerpt. Open a design in its supported host rather than renaming it to an accepted attachment type.
How to Attach Files
- Drag a supported file into the chat input area, or use the attachment picker.
- Confirm that the intended file appears in the composer.
- Choose a supported model and mode.
- Write a question that identifies the relevant content.
- Send and check any upload progress or error before treating the file as available.
You can add multiple supported files. Refer to each by filename so the assistant does not confuse a datasheet, schematic screenshot, and measured capture.
Datasheet Workflows
Attach the exact document revision and package information, then ask:
Read the pinout figure for this exact package in the attached PDF.
Compare it with the selected symbol and footprint.
List any missing or ambiguous pin mapping; do not edit the design.
For a reference circuit:
Review the application circuit on page 12 for my stated supply
and load conditions. Separate required components from optional
examples. Plan any proposed changes before implementation.
An accepted PDF does not mean every page, table, or drawing was read accurately. Check the original source for pin numbers, units, tolerances, and operating conditions. If content is missing, ask about a smaller section or provide a readable excerpt.
Attaching a datasheet to chat does not automatically associate it with a library component. See Component Editor for generation, review, and installation.
In compatible native builds, Preferences → AI Workflows → Download datasheets on this computer when Trace's servers are blocked enables a local-download fallback. It is On by default and still sends the downloaded PDF to the assistant. A website can refuse both paths; check the acquisition result and actual document revision rather than assuming the requested source was read.
SPICE Model Attachments
For a compatible native schematic session, attach the model text or ZIP containing its required include files. Identify the exact component, package, model name, and source. Ask Trace to inspect the available model declarations before installing.
Inspect the attached SPICE model for this exact component.
List its declared model names and terminal order.
Before installation, check the current symbol pins and power units.
Report unsupported syntax or translation limits; do not substitute a part.
Installation is a separate Agent action with an explicit pin association. An accepted attachment or listed model is not an installed binding or a successful run. Keep all required include files and read any compatibility or provisional-model findings. See Simulation for the full sequence.
Compatible companion builds can also read/install models when their bundled simulation engine and selected schematic support it. See companion simulation for host-specific limits. File acceptance alone never proves engine availability, valid model syntax, or successful installation.
Image Workflows
In compatible builds, GPT Astra and GPT Sol support direct image input. Trace Genie 2.0 Flash and Trace Genie 2.0 are text-only; a supported workflow may provide an image description instead. Host support varies, and descriptions may omit small labels or details. See Models.
Start by verifying interpretation:
Describe the attached sketch. List the component values and
connections you can actually read, and mark unclear details.
Do not recreate it in CAD yet.
For a measured capture, include the probe location, scale, units, and operating conditions. A picture of a waveform alone does not prove its cause or certify the circuit. A board photograph does not reveal hidden routing or guarantee component identification.
BOM and Specification Documents
The shared picker does not directly upload CSV or Markdown. Add supported reusable documents through Artifacts, select the intended file with @, and state the task.
For a short specification, paste the actual requirements into chat. For a PDF specification, use the normal picker within its limit. Do not assume an Artifacts storage limit also applies to direct attachments or that a stored file has finished indexing.
How Context Persists
Follow-up turns can reference previously attached documents. Use the filename and page rather than “that file,” especially when several sources are present.
Long conversations may summarize older context. A summary is not a guarantee that every numeric limit or figure remains available. Recheck the original document for important decisions, or mention the reusable source again.
Context Window Indicator
Where shown, the context meter indicates how much conversation context is in use. It is not upload progress, a document completeness check, or evidence that all attachment content was read.
For a new topic, start a separate conversation and provide its required context. Do not assume files or requirements automatically transfer to another chat or account.
If an Attachment Fails
- Too large: use a smaller relevant PDF excerpt or a supported reusable-file workflow.
- Unsupported type: paste relevant text or use Artifacts; do not change only the extension.
- Image cannot be handled: choose a supported model for an unsent request, or provide the necessary details as text.
- Uncertain send: check the original chat and task before submitting again.
Uploading context to hosted assistance can transmit the selected file. Only provide material you intend to share through that service.
For scoped prompts and safe send recovery, see Using Prompts and Chat.