logoredraws.com

Pixel Brush in FireAlpaca: Settings and Checks for Crisp Favicon Pixels

How to get hard-edged, single-pixel strokes in FireAlpaca for favicon work, the order of checks when strokes come out soft, and what this means for vector logo sources.

Published

Contents
  1. The short answer
  2. Setting up a hard-edged pixel brush
  3. Order of checks when strokes come out soft
  4. Observable file properties versus visual judgment
  5. Working from a vector logo
  6. Export and permission caveats
  7. Gaps in the available evidence

The short answer

FireAlpaca does not need a special plug-in to paint pixel by pixel. A hard-edged brush at a whole-number size, with anti-aliasing, pressure-driven size or opacity, and stroke smoothing switched off, places solid pixels on the canvas grid. Soft or partly transparent edges usually come from one of those settings, from the brush type itself, or from a later resize or export step. Menu and option names can differ between FireAlpaca versions and operating systems, so confirm each setting in your own installation rather than relying on an exact label.

For favicon work this matters because a favicon is shown at very small pixel dimensions, where a single semi-transparent edge pixel can make a logo mark look blurred. FireAlpaca is a raster editor, so whatever you paint with a pixel brush is a grid of pixels, not vector paths. It is suited to the final hand-refinement stage of a favicon, not to building or editing the vector logo itself.

Setting up a hard-edged pixel brush

  • Choose a hard brush such as the pen or pencil type rather than airbrush, watercolor, blur or other soft-edged brushes.
  • Set the brush size to a whole number; size 1 places one pixel per dab.
  • Turn off anti-aliasing for the brush if your version offers that option, so edges are not blended with partial transparency.
  • Disable pen-pressure control of size and opacity, or use a mouse, so stroke width and density stay constant.
  • Set stroke correction or stabilizer to its lowest value, since smoothing can shift where pixels land.
  • Keep brush opacity at full strength unless you intend to place a deliberately lighter pixel.
  • Apply the same no-anti-aliasing approach to the eraser and the fill bucket, so cleanup and fills do not reintroduce soft edges.

Order of checks when strokes come out soft

If pixels still look blurry, check causes from the brush outward to the exported file. This order isolates the problem quickly because each step rules out one stage of the pipeline.

  • 1. Brush type: confirm you are not using a brush that is soft by design.
  • 2. Edge setting: confirm anti-aliasing is off for the active tool, not only for a different tool.
  • 3. Size: confirm the size is a whole number and is not being changed by pressure.
  • 4. Opacity: check brush opacity, layer opacity and the layer blend mode; any of these can make solid pixels look partly transparent.
  • 5. Smoothing: lower or disable stroke correction.
  • 6. Viewing zoom: inspect at 100% or a whole-number zoom such as 200% or 800%; fractional zoom levels and screen scaling can make sharp pixels look soft on screen even when the file is fine.
  • 7. Canvas size: confirm the canvas is the intended favicon pixel dimension, rather than a large canvas that will be shrunk later.
  • 8. Resizing: if the image is scaled, use nearest-neighbor style interpolation if offered; smoothing interpolation blends pixels.
  • 9. Export format: save as PNG or another lossless format with transparency; JPEG compression adds blurred, discolored edge pixels and removes transparency.

Observable file properties versus visual judgment

Some of these questions can be settled by inspecting the file, and some cannot. Pixel dimensions, file format, the presence of an alpha channel, and the exact color and opacity value of any given pixel are observable properties. Zooming in to a high whole-number level and sampling edge pixels with the eyedropper shows whether an edge is fully opaque or partly transparent. Whether a favicon reads clearly at small size, or whether a stroke looks too heavy, is a visual judgment and should be tested by viewing the exported file at its real display size.

A favicon is usually derived from a vector logo by rasterizing it at the target size and then fixing edge pixels by hand. Do not assume a source file is true vector because of its extension or because its preview looks sharp. Vector-capable formats can contain embedded raster images, and text may be live type rather than outlined paths. Inspect the source in a vector editor to confirm which parts are paths, which are live text and which are embedded bitmaps before rasterizing it.

Pixel edits made in FireAlpaca do not flow back into the vector source. Keep the vector master separate, and treat the hand-refined favicon as a size-specific raster derivative. If several sizes are needed, each small size generally benefits from its own pixel pass rather than being scaled from one refined image.

Export and permission caveats

Check which formats your FireAlpaca version can export. If it cannot produce the icon container format your site requires, export lossless PNG files at each size and assemble them with a dedicated favicon or icon tool. Separately, having access to a logo file does not grant permission to modify or publish it; confirm usage rights with the logo owner before producing derivatives.

Gaps in the available evidence

No version-specific documentation, menu paths, default values or screenshots were supplied for this article. The guidance above relies on general raster-editing principles that apply to FireAlpaca's brush and export behavior, but exact option names and locations should be verified in the version you have installed.