> ## Documentation Index
> Fetch the complete documentation index at: https://enterprise-docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Download File

> **Available for**: Chatflow, Chatbot, Agent, Text Generator apps.

Returns the raw bytes of a file previously returned by [Upload File](/en/3.11.x/develop/api/files/upload-file). A file is reachable only through the app whose messages reference it.



## OpenAPI

````yaml /en/3.11.x/develop/api/openapi_service.json get /files/{file_id}/preview
openapi: 3.0.1
info:
  title: Dify Service API
  description: >-
    REST API for Dify applications and knowledge bases. Application endpoints
    authenticate with an app API key; knowledge endpoints authenticate with a
    dataset API key.
  version: 1.0.0
servers:
  - url: https://{api_base_url}
    description: >-
      Base URL of the Dify Service API. Replace it with your deployment's API
      endpoint.
    variables:
      api_base_url:
        default: api.example.com/v1
        description: Host and path of the API base URL, without the `https://` prefix.
security:
  - ApiKeyAuth: []
tags:
  - name: Chat Messages
    description: Operations related to chat messages and interactions.
  - name: Files
    description: File upload and preview operations.
  - name: End Users
    description: Operations related to end user information.
  - name: Feedback
    description: User feedback operations.
  - name: Conversations
    description: Operations related to managing conversations.
  - name: Audio
    description: Text-to-Speech and Speech-to-Text operations.
  - name: Applications
    description: Operations to retrieve application settings and information.
  - name: Annotations
    description: Operations related to managing annotations for direct replies.
  - name: Human Input
    description: Endpoints for resuming paused workflows that require human input.
  - name: Workflow Runs
    description: Operations for executing and managing workflows.
  - name: Completion Messages
    description: Operations related to text generation and completion.
  - name: Knowledge Bases
    description: >-
      Operations for managing knowledge bases, including creation,
      configuration, and retrieval.
  - name: Documents
    description: >-
      Operations for creating, updating, and managing documents within a
      knowledge base.
  - name: Chunks
    description: Operations for managing document chunks and child chunks.
  - name: Metadata
    description: >-
      Operations for managing knowledge base metadata fields and document
      metadata values.
  - name: Tags
    description: Operations for managing knowledge base tags and tag bindings.
  - name: Models
    description: Operations for retrieving available models.
  - name: Knowledge Pipeline
    description: >-
      Operations for managing and running knowledge pipelines, including
      datasource plugins and pipeline execution.
paths:
  /files/{file_id}/preview:
    get:
      tags:
        - Files
      summary: Download File
      description: >-
        **Available for**: Chatflow, Chatbot, Agent, Text Generator apps.


        Returns the raw bytes of a file previously returned by [Upload
        File](/en/3.11.x/develop/api/files/upload-file). A file is reachable
        only through the app whose messages reference it.
      operationId: previewChatFile
      parameters:
        - name: file_id
          in: path
          required: true
          description: ID of the file to download, from the Upload File response.
          schema:
            type: string
            format: uuid
        - name: as_attachment
          in: query
          required: false
          description: >-
            When `true`, the file downloads as an attachment instead of
            rendering inline in the browser.
          schema:
            type: boolean
            default: false
        - name: user
          in: query
          required: false
          description: >-
            End-user identifier, defined by your app and unique within it. It
            has no effect on file access here, which is scoped by app and
            message rather than by `user`. See [End User
            Identity](/en/3.11.x/develop/api/guides/end-user-identity).
          schema:
            type: string
      responses:
        '200':
          description: >-
            Returns the raw file content. The `Content-Type` header is set to
            the file's MIME type. If `as_attachment` is `true`, the file is
            returned as a download with `Content-Disposition: attachment`.
          content:
            application/octet-stream:
              schema:
                type: string
                format: binary
        '403':
          description: >-
            `file_access_denied` : The file exists but belongs to a different
            app or workspace.
          content:
            application/json:
              examples:
                file_access_denied:
                  summary: file_access_denied
                  value:
                    status: 403
                    code: file_access_denied
                    message: Access to the requested file is denied.
        '404':
          description: >-
            `file_not_found` : No file with this ID is reachable through this
            app's messages.
          content:
            application/json:
              examples:
                file_not_found:
                  summary: file_not_found
                  value:
                    status: 404
                    code: file_not_found
                    message: The requested file was not found.
components:
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: API_KEY
      description: >-
        Every request authenticates with an API key: `Authorization: Bearer
        {API_KEY}`. App endpoints take an app API key; knowledge endpoints take
        a knowledge base API key ([Get
        Started](/en/3.11.x/develop/api/guides/get-started)).


        Keep keys server-side; never embed them in client code. Requests with a
        missing or invalid key fail with HTTP `401` (`unauthorized`).

````