Skip to content

docs: WanImageToVideo FPS, ComfyUI Manager update, memory offload defaults (consolidated)#1272

Open
lin-bot23 wants to merge 4 commits into
Comfy-Org:mainfrom
lin-bot23:analytics-fix/2026-07-15-memory-offload-defaults
Open

docs: WanImageToVideo FPS, ComfyUI Manager update, memory offload defaults (consolidated)#1272
lin-bot23 wants to merge 4 commits into
Comfy-Org:mainfrom
lin-bot23:analytics-fix/2026-07-15-memory-offload-defaults

Conversation

@lin-bot23

@lin-bot23 lin-bot23 commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Consolidated PR merging 3 related changes from the 2026-07-15 analytics batch that had overlapping file changes:

Changes

  1. WanImageToVideo output frame rate (built-in-nodes/WanImageToVideo.mdx) — Added note confirming Wan video uses fixed 16 FPS with duration calculation example.

  2. ComfyUI Manager update instructions (installation/update_comfyui.mdx) — Added section covering Manager UI, Git, and Portable version update methods.

  3. Memory offloading default behavior (development/comfyui-server/startup-flags.mdx) — Added summary that async weight offloading and dynamic VRAM are enabled by default on Nvidia GPUs.

Supersedes

Checklist

  • English only (translations separate)
  • PR created by Hermes Agent (bot), do not merge

Users commonly ask what frame rate the WanImageToVideo node outputs at.
The length parameter gives frame count but FPS was undocumented. Wan
video generation uses a fixed 16 FPS, documented in tutorial workflows
but missing from the node reference docs.

Source: Mintlify AI Assistant analytics data (2026-07-15)
Users asked about updating ComfyUI Manager, which is a separate custom
node from ComfyUI core. The update page covered ComfyUI itself but
did not mention how to update Manager. Adds three methods: via Manager
UI, via Git pull, and notes for the Portable version.

Source: Mintlify AI Assistant analytics data (2026-07-15)
Users commonly ask whether memory offloading is on by default. The
flag table listed defaults per-flag but there was no summary of the
combined default behavior. This adds a sentence explaining that async
weight offloading and dynamic VRAM are enabled by default on Nvidia GPUs.

Source: Mintlify AI Assistant analytics data (2026-07-15)
@lin-bot23 lin-bot23 changed the title docs: add memory offloading default summary to startup flags page docs: WanImageToVideo FPS, ComfyUI Manager update, memory offload defaults (consolidated) Jul 15, 2026
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Documentation now records Nvidia defaults for VRAM flags and adds ComfyUI Manager update instructions for UI, Git, and portable Windows installations, including the --enable-manager recovery flag.

Changes

Startup flag defaults

Layer / File(s) Summary
Document VRAM defaults
development/comfyui-server/startup-flags.mdx
States that --async-offload and --enable-dynamic-vram are enabled by default on Nvidia GPUs and references platform-specific defaults.

ComfyUI Manager updates

Layer / File(s) Summary
Document Manager updates
installation/update_comfyui.mdx
Adds Manager UI, Git, and portable Windows update procedures, plus instructions to re-enable the Manager with --enable-manager.

Suggested reviewers: comfyui-wiki

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified code

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

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

@coderabbitai
coderabbitai Bot requested a review from comfyui-wiki July 22, 2026 05:42

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@installation/update_comfyui.mdx`:
- Line 136: Update the opening ComfyUI Manager description in the installation
documentation to state that its separate custom-node update workflow applies to
manual installations, while Portable installations bundle Manager with ComfyUI
and update it through the core process. Ensure the corresponding wording at the
additionally affected Manager description remains consistent.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5de15728-e17d-4a90-97e9-db4045c8e849

📥 Commits

Reviewing files that changed from the base of the PR and between 4970189 and 6458ab2.

📒 Files selected for processing (2)
  • development/comfyui-server/startup-flags.mdx
  • installation/update_comfyui.mdx


## How to Update ComfyUI Manager

ComfyUI Manager is a custom node that provides installation and management of other custom nodes, models, and snapshots. It is separate from the ComfyUI core code and has its own update process.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Clarify that Manager’s update model depends on the installation type.

Line 136 says Manager is separate from ComfyUI core and has its own update process, but the Portable section says it is bundled into core and updated with ComfyUI. Make the opening description explicitly scope the separate custom-node workflow to manual installations. Otherwise the docs tell a split-brain update story.

Suggested wording
-ComfyUI Manager is a custom node that provides installation and management of other custom nodes, models, and snapshots. It is separate from the ComfyUI core code and has its own update process.
+ComfyUI Manager provides installation and management of other custom nodes, models, and snapshots. Its update process depends on the installation type: manual installations manage it separately, while Windows Portable bundles it into ComfyUI core.

Also applies to: 159-160

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@installation/update_comfyui.mdx` at line 136, Update the opening ComfyUI
Manager description in the installation documentation to state that its separate
custom-node update workflow applies to manual installations, while Portable
installations bundle Manager with ComfyUI and update it through the core
process. Ensure the corresponding wording at the additionally affected Manager
description remains consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant