Skip to content

docs: add FAQ entry for embedding import on Comfy Cloud #1256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lin-bot23 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add FAQ entry for embedding import on Comfy Cloud #1256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions cloud/import-models.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,4 +145,8 @@ Make sure your API key has the necessary permissions to access the specific priv
<Accordion title="Can I delete a model that I uploaded?">
Yes. You can delete models you imported. Note that models uploaded by the Comfy internal team cannot be deleted.
</Accordion>

<Accordion title="Can I import embedding or textual inversion files?">
Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`).
Comment on lines +149 to +150

@coderabbitai coderabbitai Bot Jul 12, 2026

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 | 🟠 Major | ⚡ Quick win

Reconcile this FAQ with the upload restriction above.

Line 122 says only safetensor files are supported, while this FAQ claims .pt and .bin imports work. Clarify whether the restriction applies only to standard model uploads, or update one of the conflicting claims.

🤖 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 `@cloud/import-models.mdx` around lines 149 - 150, Reconcile the supported file
formats between the upload restriction near line 122 and the FAQ accordion
titled “Can I import embedding or textual inversion files?”. Clarify that the
restriction applies only to standard model uploads if embeddings and textual
inversion files may use .pt and .bin, or remove those formats from the FAQ so
both sections state the same supported behavior.

@coderabbitai coderabbitai Bot Jul 12, 2026

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

Remove the backslashes from inline code spans.

The ``` sequences escape the backticks, so these values may render as literal backticks instead of code-styled tokens. Keep the syntax crisp, not cryptic.

Proposed fix 
-    Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`).
+    Yes. Embedding and textual inversion files (supported formats: `.safetensors`, `.pt`, `.bin`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your `CLIPTextEncode` node prompt with the embedding syntax (for example, `embedding:my-embedding-name`).
📝 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
Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`).
Yes. Embedding and textual inversion files (supported formats: `.safetensors`, `.pt`, `.bin`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your `CLIPTextEncode` node prompt with the embedding syntax (for example, `embedding:my-embedding-name`).
🤖 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 `@cloud/import-models.mdx` at line 150, Update the inline code spans in the
import guidance to use unescaped backticks for the supported file extensions,
CLIPTextEncode, and embedding syntax; preserve the existing wording and
examples.

</Accordion>
</AccordionGroup>
Loading