title: "Attachment Integration: Attaching Screenshots and Documentation",

summary:

"How DevSpeak processes uploaded files, when attachments are sent inline versus through document workflows, and how attachment metadata is preserved.",

category: "advanced-configuration",

tags: [

"attachments",

"uploaded-files",

"document-translation",

"attachment-manifest",

"file-context",

],

lastReviewed: "2026-04-08",

};

Attachment Integration: Attaching Screenshots and Documentation

Attachments give DevSpeak more context than raw text alone. They are especially useful when a request depends on UI structure, existing markdown, diagrams, screenshots, or source documents that should shape the generated output.

What This Page Covers

  • Which file types work well as attachments.

  • How DevSpeak chooses inline processing versus file-backed workflows.
  • What metadata is preserved when attachments are saved with translation history.

    • Why Attachments?

    Attachments are a powerful tool for providing visual context and supplementary information that may be difficult to convey through text alone. For example, a screenshot of a user interface can help the LLM understand the layout and functionality of a feature request.

    How to Attach Files

    To attach a file, drag it into the translation workspace or use the upload control before generating output. DevSpeak supports common image formats, markdown, plain text, and larger document workflows such as PDF translation.

    Processing Paths

    DevSpeak does not treat every file the same way.

  • Images and text-like assets: These can be sent inline when the generation path supports them.
  • Large documents: PDF and document-heavy flows are processed through the async document-job path.
  • History-aware uploads: Attachment metadata is stored alongside the translation so the request can be re-opened later without losing context.

    • Impact on Output

    Attachments are not rendered as decorative uploads. They become part of the request context that shapes the resulting specification, prompt, or refined output.

  • A screenshot can anchor UI descriptions and interaction details.
  • A markdown or text file can preserve terminology that should carry into the generated result.
  • A document job can extract larger source material and reassemble the translated output through chunked processing.

    • Saved Metadata

    When a translation is persisted, DevSpeak stores attachment references with fields such as uploaded file details and attachment-manifest metadata. This makes it possible to hydrate historical records and re-open translation sessions with the same supporting context.

    Best Practices

    When attaching files, consider the following best practices:

  • Provide clear, high-quality images: Ensure that screenshots and diagrams are legible and relevant to the translation request.
  • Use descriptive file names: Give your files meaningful names that clearly indicate their content and purpose.
  • Keep the set intentional: Add only files that improve context; unrelated uploads slow the workflow and dilute the prompt.