Action

Favicon package

Image → favicon.ico + PNGs (.zip)

Takes a single image and produces the whole set of website icon files (the little browser-tab icon plus app icons), packaged as a downloadable zip sized for every browser and device.

How it works

A favicon is the tiny icon that shows in a browser tab, on a bookmark, and on a phone home screen when someone saves your site. Modern sites need that icon in many sizes and formats, which is tedious to make by hand.

This node does the whole set from one picture. You give it a single image and it returns the classic favicon.ico file plus the range of PNG sizes browsers and phones expect, all bundled into one zip you can hand to a web developer or drop into a site.

It is a one-and-done branding utility. The output is a zip file, so it typically flows straight to storage or download rather than into more document steps.

Common use cases

Real situations where this node earns its place in a flow.

Full favicon set from one logo

Turn a single image into the .ico and PNGs a website needs across browsers and devices.

Refresh site icons

Produce an updated favicon package whenever a brand changes.

A client deliverable

Generate the whole icon zip as part of a website build hand-off.

Favicon package in a workflow

A simple example of where this node sits in a flow.

What you set up

Provide one source image (a square logo or mark gives the cleanest result).
Run the node to generate the full icon set as a single zip.
Route the zip to storage or download so someone can add it to a website.

Common questions

What image should I start from?

A square, high-resolution logo works best. Icons get shrunk very small, so a simple mark stays recognizable while a detailed photo turns into a blur.

Why a zip instead of a single icon?

Browsers and phones each want their own sizes and the .ico format, so the node makes all of them at once and packs them together so nothing is missed.

Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.

Field	Type	Default	What it controls
`icoSizes`	string	`16,32,48`	Comma-separated icon sizes for the .ico (16,32,48,64,128,256).
`background`	string	—	Background fill for padded icons; empty means transparent.
`appName`	string	—	App name written into the generated web manifest.
`filenameTemplate`	string	`favicons`	Template for the output zip filename.

icoSizes
Comma-separated icon sizes for the .ico (16,32,48,64,128,256).
Type: stringDefault: 16,32,48
background
Background fill for padded icons; empty means transparent.
Type: string
appName
App name written into the generated web manifest.
Type: string
filenameTemplate
Template for the output zip filename.
Type: stringDefault: favicons

How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.

{
  "id": "favicon",
  "type": "card",
  "position": {
    "x": 160,
    "y": 120
  },
  "data": {
    "type": "favicon",
    "kind": "processor",
    "title": "Favicon package",
    "subtitle": "Image → favicon.ico + PNGs (.zip)",
    "config": {
      "icoSizes": "16,32,48",
      "background": "",
      "appName": "",
      "filenameTemplate": "favicons"
    }
  }
}