docs: update file size limit to 1024 mb

[mendonk]

Release 1.5.0.post2 includes the change for increasing the default file size.
This updates the value in docs.

Summary by CodeRabbit

• Documentation
  • Updated API, Components, and Concepts docs to reflect the new default upload size limit of 1024 MB (up from 100 MB).
  • Clarifies limits for image and general file uploads across v1/v2 flows; override instructions via environment configuration remain unchanged.
  • Aligns all end-user guidance with current service defaults; no functional or API changes.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Documentation updates changed the stated default maximum upload file size from 100 MB to 1024 MB across API reference, components, and concepts docs. No code or API changes.

Changes

Cohort / File(s)	Summary of changes
Docs: Default max upload size text update docs/docs/API-Reference/api-files.mdx, docs/docs/Components/components-data.mdx, docs/docs/Concepts/concepts-file-management.mdx	Updated default maximum file size from 100 MB to 1024 MB; environment variable guidance unchanged; no behavioral or API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• ref: Increase max file upload size to 1024 MB #9276 — Updates documentation reflecting a code change setting default max upload size to 1024 MB.

Suggested labels

lgtm

Suggested reviewers

• Cristhianzl
• jordanrfrazier

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs-increase-max-file-upload

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 3

🔭 Outside diff range comments (3)

docs/docs/Concepts/concepts-file-management.mdx (1)

1-4: Add required frontmatter description

Docs guidelines require a description in frontmatter.

 ---
 title: Manage files
+description: Learn how to upload, manage, and use files in Langflow, including default upload limits and how to configure them.
 slug: /concepts-file-management
 ---

docs/docs/API-Reference/api-files.mdx (1)

1-4: Add required frontmatter description

Add a short description per docs guidelines.

 ---
 title: Files endpoints
+description: Learn how to upload, list, download, and manage files with the Langflow API, including upload size limits and configuration.
 slug: /api-files
 ---

docs/docs/Components/components-data.mdx (1)

1-4: Add required frontmatter description

Frontmatter is missing a description.

 ---
 title: Data
+description: Explore Langflow Data components for loading files, directories, URLs, and APIs, including file size limits and supported types.
 slug: /components-data
 ---

🧹 Nitpick comments (1)

docs/docs/Components/components-data.mdx (1)

117-119: Optional: Add a brief note about external upload limits

Consider adding a short tip that large uploads may also be constrained by reverse proxies (for example, Nginx client_max_body_size) or hosting providers, even if Langflow allows 1024 MB.

Example insertion after the paragraph:

:::tip
Your deployment environment may enforce additional upload limits (for example, reverse proxy or hosting provider). Ensure those limits are configured to allow files up to 1024 MB if needed.
:::

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these settings in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 75970e5 and 506f609.

📒 Files selected for processing (3)

• docs/docs/API-Reference/api-files.mdx (2 hunks)
• docs/docs/Components/components-data.mdx (1 hunks)
• docs/docs/Concepts/concepts-file-management.mdx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

docs/docs/**/*.{md,mdx}

📄 CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)

docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.

Files:

• docs/docs/Components/components-data.mdx
• docs/docs/Concepts/concepts-file-management.mdx
• docs/docs/API-Reference/api-files.mdx

🔇 Additional comments (2)

docs/docs/API-Reference/api-files.mdx (2)

64-66: Updated default limit to 1024 MB — consistent with release notes

Text and env var name look correct here. No further action.

---

243-244: v2 section limit text is consistent

The default limit and configuration reference match the v1 section and the rest of the PR.

[coderabbitai]

🛠️ Refactor suggestion

Default size text OK; align config name with API docs

This section calls out --max-file-size-upload as an environment variable; in API docs you use LANGFLOW_MAX_FILE_SIZE_UPLOAD. Recommend mirroring both the env var and the CLI flag and fixing the terminology.

-By default, the maximum file size is 1024 MB.
-To modify this value, change the `--max-file-size-upload` [environment variable](/environment-variables).
+By default, the maximum file size is 1024 MB.
+To modify this value, set the `LANGFLOW_MAX_FILE_SIZE_UPLOAD` environment variable or use the `--max-file-size-upload` CLI flag. See [environment variables](/environment-variables).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	By default, the maximum file size is 1024 MB.
	To modify this value, change the `--max-file-size-upload` [environment variable](/environment-variables).
	By default, the maximum file size is 1024 MB.
	To modify this value, set the `LANGFLOW_MAX_FILE_SIZE_UPLOAD` environment variable or use the `--max-file-size-upload` CLI flag. See [environment variables](/environment-variables).

🤖 Prompt for AI Agents

In docs/docs/Components/components-data.mdx around lines 117 to 119, the text
references only the CLI flag `--max-file-size-upload` while the API docs use the
environment variable `LANGFLOW_MAX_FILE_SIZE_UPLOAD`; update this section to
mention both the CLI flag and the environment variable (e.g., state default is
1024 MB and that it can be changed via the CLI flag `--max-file-size-upload` or
the environment variable `LANGFLOW_MAX_FILE_SIZE_UPLOAD`), and correct
terminology to explicitly label which is the "CLI flag" and which is the
"environment variable" with a link to the environment-variables page for the env
var.

[coderabbitai]

🛠️ Refactor suggestion

Default size update looks good; fix config knob naming for consistency

The sentence calls --max-file-size-upload an environment variable. Elsewhere in this PR (API docs) you use LANGFLOW_MAX_FILE_SIZE_UPLOAD, which looks like the environment variable, while --max-file-size-upload is a CLI flag. Clarify and align.

Apply this diff to make both options explicit and consistent:

-By default, the maximum file size is 1024 MB.
-To modify this value, change the `--max-file-size-upload` [environment variable](/environment-variables).
+By default, the maximum file size is 1024 MB.
+To modify this value, set the `LANGFLOW_MAX_FILE_SIZE_UPLOAD` environment variable or pass the `--max-file-size-upload` CLI flag. See [environment variables](/environment-variables).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	By default, the maximum file size is 1024 MB.
	To modify this value, change the `--max-file-size-upload` [environment variable](/environment-variables).
	By default, the maximum file size is 1024 MB.
	To modify this value, set the `LANGFLOW_MAX_FILE_SIZE_UPLOAD` environment variable or pass the `--max-file-size-upload` CLI flag. See [environment variables](/environment-variables).

🤖 Prompt for AI Agents

In docs/docs/Concepts/concepts-file-management.mdx around lines 96 to 97, the
text incorrectly labels the CLI flag as an environment variable and is
inconsistent with the API docs; update the sentence to explicitly document both
the CLI flag and the environment variable (use --max-file-size-upload for the
CLI flag and LANGFLOW_MAX_FILE_SIZE_UPLOAD for the env var), clarify which one
to change to modify the default 1024 MB, and ensure the environment variable
links to the /environment-variables page.

---

💡 Verification agent

🧩 Analysis chain

Verify target page and config usage across docs

Please confirm:

• The /environment-variables page exists (slug) and documents both the LANGFLOW_MAX_FILE_SIZE_UPLOAD env var and the --max-file-size-upload flag.
• No remaining references incorrectly call a CLI flag an environment variable.

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Check that an environment-variables doc exists with the expected slug..."
rg -n --line-number $'^slug:\\s*/environment-variables\\s*$' docs/docs -A 2 || true

echo
echo "Occurrences of the two configuration knobs across docs:"
echo "---- LANGFLOW_MAX_FILE_SIZE_UPLOAD ----"
rg -n --line-number 'LANGFLOW_MAX_FILE_SIZE_UPLOAD' docs/docs || true
echo "---- --max-file-size-upload ----"
rg -n --line-number '\-\-max-file-size-upload' docs/docs || true

echo
echo "Spot any lines that call a CLI flag an environment variable:"
rg -n --line-number 'environment variable.*--max-file-size-upload' docs/docs || true

Length of output: 2766

---

Action: Fix docs that call the CLI flag an environment variable

Short summary: The /environment-variables page exists and documents LANGFLOW_MAX_FILE_SIZE_UPLOAD (and links to the --max-file-size-upload CLI flag), but two docs incorrectly refer to the CLI flag as an environment variable.

Files to fix:

• docs/docs/Concepts/concepts-file-management.mdx:97 — currently: "To modify this value, change the --max-file-size-upload environment variable."
  Suggested replacement:

  By default, the maximum file size is 1024 MB.
  To modify this value, change the `LANGFLOW_MAX_FILE_SIZE_UPLOAD` [environment variable](/environment-variables) or use the `--max-file-size-upload` CLI flag.
  

• docs/docs/Components/components-data.mdx:118 — same incorrect wording; apply the same replacement.

Notes:

• Confirmed /environment-variables at docs/docs/Configuration/environment-variables.mdx (slug: /environment-variables) contains LANGFLOW_MAX_FILE_SIZE_UPLOAD and links to the CLI flag.
• Leave references that correctly point to the env var (or link to the CLI reference) as-is.

🤖 Prompt for AI Agents

In docs/docs/Concepts/concepts-file-management.mdx around lines 96-97 (and also
update docs/docs/Components/components-data.mdx around line 118), replace the
incorrect wording that calls the CLI flag an environment variable; change the
text to mention the actual environment variable and the CLI flag, e.g. "By
default, the maximum file size is 1024 MB. To modify this value, change the
LANGFLOW_MAX_FILE_SIZE_UPLOAD [environment variable](/environment-variables) or
use the --max-file-size-upload CLI flag." Ensure links remain to
/environment-variables and keep any correct references to the env var or CLI
elsewhere unchanged.

[edwinjosechittilappilly]

Mendon I believe the 1.5.0post2 doesn't have the file limit increase, only the remix template update.

[mendonk]

Mendon I believe the 1.5.0post2 doesn't have the file limit increase, only the remix template update.

I'll point this PR at the 1.6 branch then

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft