09 ZMongo Content Pack Add Images
Splat a whole batch of images into a content pack — ZMongo 09 Content Pack Add Images
- content_pack
- images
- content_pack
- content_pack_json
- manifest_json
- preview_markdown
- aliases
- data_types
- indexed
- success
09 Content Pack Add Images is the batch sibling of 09 Content Pack Add Image. Instead of one image, it takes an entire IMAGE batch and writes each frame as its own typed field in a content pack, numbered like image00, image01, image02… This is the node for "I generated a grid / a contact sheet / an animation frame set, and I want the whole set bundled in one portable record."
Content packs are ZMongo's transportable asset bundles - a ZMONGO_CONTENT_PACK holding typed fields (images, text, numbers) that you can save to the database, share, or drop back into a canvas. The Add Images node is what you use when one image isn't enough.
How it works
The node splits the incoming batch into individual frames and encodes each to an inline base64 PNG, then appends one field per frame. The naming is controlled by:
field_alias_prefix- base name (defaultimage), producingimage00,image01, …label_prefix- human labels (defaultImage).source_path_prefix- provenance metadata (defaultload_image.images).storage_mode- single choice,inline_base64_png.replace_existing_prefix- default true: re-adding replaces the old numbered set.
The optional inputs are the ones to actually tune: start_index (where numbering begins, default 0), max_images (cap, 1–256, default 16), and index_padding (digits in the number, default 2 → image00, set 0 → image0).
Outputs mirror the rest of the family: updated content_pack, content_pack_json, manifest_json, preview_markdown, aliases, data_types, indexed, and success.
The inputs and outputs that matter
content_pack- required.images- required, the batch.max_images- your sanity cap. A 256-frame batch encoded as base64 PNGs makes a large pack; set this thoughtfully.index_padding- cosmetic, but it changes the alias names you'll address later.
Chain the content_pack output into the next pack node or into 09 Content Pack Save.
Install
Standard:
cd ComfyUI/custom_nodes
git clone https://github.com/CentralFloridaAttorney/ComfyUI-ZMongo
cd ComfyUI-ZMongo
pip install -r requirements.txt
or ComfyUI Manager → "ComfyUI-ZMongo" → restart. No session, no model downloads - pure in-memory work.
Troubleshooting
success: false- encoding a frame failed; checkpreview_markdownfor which one. A batch with unusual dimensions or a non-float tensor is the usual suspect.- Missing frames -
max_imagescaps the batch (default 16). If you have 40 frames, raise it. - Alias names you didn't expect -
index_paddingandstart_indexdetermine the names.image00vsimage0vsimageall change how you retrieve fields later. - Pack got huge - inline base64 on many images is heavy. If the pack is bloating, consider resizing before adding or using fewer frames.
Add Images is the tool when your "asset" is a set, not a single frame - grids, pose sheets, animation passes. It turns a batch of renders into one field-set you can save and rehydrate as a unit.
Inputs (11)
| Name | Type | Default | Description |
|---|---|---|---|
| content_pack | ZMONGO_CONTENT_PACK | — | |
| images | IMAGE | — | |
| field_alias_prefix | STRING | image | — |
| label_prefix | STRING | Image | — |
| source_path_prefix | STRING | load_image.images | — |
| storage_mode | COMBO | inline_base64_png | 1 options: inline_base64_png |
| replace_existing_prefix | BOOLEAN | true | — |
| start_indexopt | INT | 00–100000 | — |
| max_imagesopt | INT | 161–256 | — |
| index_paddingopt | INT | 20–8 | — |
| refresh_tokenopt | STRING | — |
Outputs (8)
| Name | Type | Description |
|---|---|---|
| content_pack | ZMONGO_CONTENT_PACK | — |
| content_pack_json | STRING | — |
| manifest_json | STRING | — |
| preview_markdown | STRING | — |
| aliases | * | — |
| data_types | * | — |
| indexed | STRING | — |
| success | BOOLEAN | — |