Why must large marketing icons be sized from the maximum real display?
Route `fontawesome-large-icon-png` (font_awesome_to_png.large) covers hero banners, campaign landings, and print-ready panels that need high-resolution PNGs for projection or large-format output. Raster upscaling exposes jaggies, so derive pixel dimensions from the maximum physical size. Marketing also layers icons on gradients and photos—transparent PNG anti-aliasing shifts per background, so maintain on-light and on-dark variants. Document padding, corner radii, and minimum legible distance so seasonal pages stay on-brand.
Exporting large marketing PNGs
- In `fontawesome-large-icon-png`, set target width/height (e.g., 256px) plus safe padding, and choose solid versus outline styles.
- Export separate colorways for gradients or photography backplates to avoid gray halos.
- Ship @1x/@2x bundles into the component library with changelog entries and license notes.
Font Awesome to PNG (large) Q&A
How do marketing heroes keep icon sizing aligned with design comps?
Export from the largest real display size first, then derive @2x/@3x assets—never upscale from a tiny master.
Edges look soft on Retina—should we distrust export density or CSS scaling first?
Reserve fixed safe zones in hero art; bake identical padding into export scripts to stop hand-tuned drift.
When headlines localize per market, do icon files need market-specific variants?
Before major campaigns, run visual regression against prior outlines to catch Font Awesome upgrades that change semantics.
How do marketing hero icons standardize padding and safe zones?
Encode minimum padding and grid multiples in design tokens and bake the same padding into export scripts to stop per-designer drift.
Cuts never match front-end sizes—what usually causes the gap?
CSS scaling without matching DPR-aware assets; align to logical pixels, ship @2x/@3x sets, and ban arbitrary transform upscales in components.