Core Nodes vs Custom Nodes

13 min

Overview

Not all nodes are built the same. In Floyo, you can use both core nodes and custom nodes in any workflow. Understanding the difference helps you build more effectively.

Types of Nodes

Node Type	Source	Availability
Core Nodes	Built into ComfyUI	Always available
Custom Nodes	Community or third-party	2,500+ pre-installed; more added daily

Core Nodes

Core nodes are the default set that comes with ComfyUI. These are the basics, the essential tools that power almost every workflow.

What Core Nodes Include

Category	Examples
Model loaders	Load Checkpoint, Load LoRA, Load VAE
Samplers and schedulers	KSampler, KSamplerAdvanced
Prompt inputs	CLIP Text Encode, Conditioning
Image outputs	Save Image, Preview Image
Conditioners	ControlNet Apply, Apply LoRA
Upscalers	Upscale Image, Upscale Latent
Image processing	Resize, Crop, Combine, Mask

Core nodes are stable, well-supported, and usually all you need for common workflows. If you've used ComfyUI before, you'll recognize them right away.

Custom Nodes

Custom nodes come from the broader ComfyUI community or your own team. These extend what you can do far beyond the basics.

What Custom Nodes Can Do

Use Case	Examples
Specialized LoRA loaders	Advanced LoRA stacking, conditional loading
Custom samplers	Alternative sampling algorithms
Text tools	Logic gates, advanced math, string manipulation
Animation & UI	Control nodes for scripting and batch workflows
Non-image tasks	Audio, data processing, function chaining

Floyo supports over 2,500 custom nodes, and you can load your own too. If someone has built it and shared it, you can use it.

See list of all available custom nodes on Floyo

💡 Tip: Custom nodes are what make ComfyUI so powerful. They let the community solve problems faster than any single team could.

Using Core and Custom Nodes Together

You can mix core and custom nodes freely. Most advanced workflows use a combination of both.

You don't need to know where every node comes from

If it works, it works

Hover over a node for a tooltip or inspect its inputs and outputs

Floyo makes it easy to experiment without breaking your flow.

Missing Custom Nodes

If you're loading a workflow with custom nodes not currently installed on Floyo:

A message is sent to Floyo's developers

The team works to install the missing nodes

Official turnaround time: within 72 hours

In practice, it's usually much faster

You can also proactively request custom nodes. See Requesting Custom Nodes for details.

How to Tell the Difference

In most cases, you don't need to distinguish between core and custom nodes. However, if you're curious:

Indicator	Meaning
Node pack name in browser	Custom nodes show their pack name (e.g., "ComfyUI-Impact-Pack")
Missing node errors	Usually indicates a custom node that needs installation