pictogramapp.com

In app, icon, and UI/UX design, "custom" means the visual and interaction work is created for one specific product or brand rather than adapted from a template, stock asset, or generic UI kit. It is worth pursuing when your interface or identity is part of what differentiates you — for example, a distinctive app icon that must read at small sizes, or a workflow that no existing pattern fits. It is usually not worth it when you need a standard, well-understood screen (a settings list, a login form) on a tight timeline.

What "custom" covers in each area

The Iconfactory describes itself as crafting "icons, apps, and user experiences for clients large and small" over more than 25 years — a scope that spans all four rows above, which is why "custom" in this field is rarely just one asset.

Custom vs. templates, stock assets, and UI kits

The practical difference is not quality — it is fit and ownership.

• Templates and UI kits give you a proven starting point. You trade distinctiveness and some control for speed and lower cost.
• Stock assets (icons, illustrations, fonts) are licensed for reuse. They can look right but may appear in competing products.
• Custom work is made for your constraints: your content lengths, your platform, your brand voice, your edge cases.

A useful test: if a competitor could drop in the same asset and nothing would feel wrong, it is probably not custom in any meaningful sense.

When custom design adds real value

Custom work tends to pay off when at least one of these is true:

• The icon is a primary brand touchpoint. App icons compete at very small sizes; a generic glyph gets lost.
• Your workflow differs from the norm. If users do something no standard pattern handles, a custom flow removes friction instead of forcing users into the wrong model.
• Consistency across many screens matters. A defined system (type scale, spacing, component rules) prevents drift as the product grows.
• You are in a crowded category. Distinctiveness is the point.

When off-the-shelf is the better call

• You need a standard, low-risk screen quickly (forms, lists, settings).
• You are validating an idea and expect the interface to change.
• Your budget is better spent on function than on visual identity.
• The platform's own conventions already serve users well.

These are conditions, not verdicts — a project can mix both, using a UI kit for structure and custom work for the icon and key moments.

A typical custom design process

1. Brief. Goals, audience, platforms, constraints, and what "done" looks like.
2. Research and references. Competitors, platform guidelines, and existing brand assets.
3. Concepts. A small number of distinct directions, not many variations of one.
4. Refinement. Chosen direction developed across real sizes and states.
5. Delivery. Final assets plus the rules for using them.
6. Verification. Check the icon at small sizes and in real contexts; check screens against actual content, not placeholder text.

Common pitfalls

• Scope creep. "Custom" quietly expands from one icon to a full system. Agree on deliverables up front.
• Unclear ownership. Confirm who owns the files and how they may be reused before work starts.
• Inconsistent branding. Custom assets applied without a system drift apart over time.
• Designing without real content. Placeholder text hides the problems custom work is meant to solve.

If you can state which touchpoints must be custom, which can stay standard, and who owns the result, you have enough to decide — and enough to brief the work.

Pictogram is a Mac app for replacing app icons, and it works on macOS 11.0 (Big Sur) or newer. It can customize icons for apps you installed yourself, but not apps pre-installed with macOS or apps downloaded from the App Store. Its key promise is that custom icons survive app updates. The beta is described as free on the Pictogram site.

Before You Start

Confirm these conditions, because they decide whether Pictogram is the right tool for your case:

• macOS version: Requires macOS 11.0 or newer. Big Sur qualifies.
• App source: The app must not be pre-installed with macOS and must not come from the App Store. Apps you downloaded directly from a developer's site are the intended target.
• Replacement icon: Have an image ready to use as the new icon. Prepare it before opening Pictogram so you can apply it in one pass.

If the app you want to change is Safari, Mail, Notes, or anything else that shipped with your Mac, or if you installed it through the App Store, Pictogram cannot change it. No workaround is described on the site.

Steps to Apply a Custom Icon

1. Install Pictogram. Download the beta (v0.1) from the Pictogram site and open it. The site lists it as free and created by Neil Sardesai.
2. Select an eligible app. In Pictogram, choose an app that meets both conditions above — not pre-installed, not from the App Store.
3. Apply your replacement icon. Use your prepared image as the new icon for that app.
4. Verify the result. Check the app's icon in the Dock and in Finder. If the old icon still appears, confirm the app is eligible and that the icon was applied to the correct app.

What Happens After an App Updates

Pictogram states that it preserves your custom icons after apps update themselves. This is the main reason to use it over manually swapping icon files: an update that replaces the app bundle would normally wipe a hand-made icon change, and Pictogram is built to keep your choice in place.

To confirm it worked in your setup, let an eligible app update, then re-check its icon in the Dock and Finder. If the custom icon is still there, the persistence feature is working for that app.

Limits and Choosing

Choose Pictogram if your target apps were installed outside the App Store and you want the icon to stay put through updates. If your target is an App Store or built-in app, Pictogram is not the tool for that job — the site offers no method for those apps.

Common Snags

• Icon doesn't change: The most likely cause is an ineligible app. Re-check whether it came from the App Store or shipped with macOS.
• macOS version error: Confirm you are on 11.0 or later.
• Beta behavior: v0.1 is a beta, so treat unexpected behavior as possible and re-verify icons after updates.

Pictogram is a macOS utility that lets you replace an app's default icon with a custom one, and it keeps that custom icon in place even after the app updates itself. It works only on macOS 11.0 (Big Sur) or newer, and it cannot change icons for apps that came pre-installed with macOS or apps downloaded from the App Store. If the app you want to restyle is a third-party app installed outside the App Store, Pictogram is built for that case; if it's a system app or an App Store app, Pictogram won't help.

What Pictogram actually does

The core job is narrow and specific: apply a custom icon to a Mac app and make it stick. That second part matters. Many manual icon-swap methods break the moment an app updates, because the update replaces the app bundle and wipes the custom artwork. Pictogram is designed to preserve your custom icons through those updates, so you don't have to redo the work each time an app ships a new version.

The tool is distributed as a beta (version 0.1 at the time of the source page) and is described as free to try. It was created by Neil Sardesai.

Which app icons it can and cannot change

The two exclusions are the practical decision point. System apps like the ones Apple ships with macOS are off-limits, and so is anything you installed through the App Store. That rules out a large share of the apps on a typical Mac, so check your target app before downloading.

How to check whether your app qualifies

1. Locate the app in Finder (usually the Applications folder).
2. Determine how it was installed: if you got it from the App Store, it's excluded; if it's a built-in macOS app, it's excluded.
3. If it's a third-party app you installed directly (for example, from a developer's website or a downloaded installer), it falls within Pictogram's supported range.
4. Confirm your Mac runs macOS 11.0 or newer.

If all four checks pass, Pictogram is a candidate for that app.

Requirements and current status

• OS: macOS 11.0 (Big Sur) or newer. Older versions are not supported.
• Distribution: available as a beta, version 0.1, described on the source page as free to try.
• Scope: custom icons for eligible third-party apps, with persistence across app updates.

Because this is an early beta, treat it as a tool for experimenting with eligible apps rather than a finished, broadly supported product. The source page does not detail pricing beyond the beta being free to try, so don't assume terms for later versions.

When to use it — and when not to

Use Pictogram if you want a consistent, personalized look across third-party Mac apps you installed yourself, and you're tired of custom icons reverting after every update. The update-preservation feature is the main reason to choose it over manual icon replacement.

Skip it if the apps you most want to restyle are Apple's built-in apps or App Store downloads — those are explicitly out of scope, and no amount of configuration will change that. In that case, look for alternatives that support App Store or system apps, or accept that those icons stay as they are.

A quick way to decide: list the apps whose icons bother you, mark each as system, App Store, or direct-install, and see whether any direct-install apps remain. If none do, Pictogram won't solve your problem.

OpenMTP is a free, open-source macOS app that moves files between a Mac and any MTP device — Android phones, Kindle, Garmin watches, FujiFilm cameras, and Meta Quest VR headsets — over a USB cable, with no Wi-Fi setup or account required. It works on macOS 10.14 (Mojave) or higher for both Apple Silicon and Intel Macs, and the official site reports 5–6x faster copies than typical alternatives plus support for 4GB+ files. Use it if you want a plug-and-play, drag-and-drop transfer tool; if you're on macOS 10.13 or earlier, you'll need the older v3.1.15 with Legacy MTP mode instead.

Before you start

• A Mac running macOS 10.14 (Mojave) or higher. macOS 10.13 and earlier have limited support and require OpenMTP v3.1.15 in Legacy MTP mode.
• An Android device (or other MTP device) and a USB cable that supports data transfer, not just charging.
• No account, cloud service, or Wi-Fi network is needed.

Step 1: Download and install OpenMTP

1. Go to the official site and download the build that matches your Mac:
   • Apple Silicon (M1 and later)
   • Intel Mac
2. Drag OpenMTP into your Applications folder.
3. Alternatively, install it with Homebrew:

brew install openmtp --cask

If you're on macOS 10.13 or earlier, download v3.1.15 instead and follow the legacy installation steps on the site.

Step 2: Connect your phone over USB

1. Plug the phone into your Mac with the USB cable.
2. Unlock the phone.
3. Tap the USB notification and choose File transfer (MTP mode).

OpenMTP detects the device right away — no Wi-Fi pairing or account sign-in.

Step 3: Move your files

The interface is a split pane: your Mac on the left, your phone on the right.

• Drag and drop files across the panes.
• Or copy and paste: select files and use ⌘C, then ⌘V in the target pane.
• Switch between internal memory and SD card from the toolbar.

Features that speed up the work

OpenMTP 3.0 introduced Kalam, a new MTP kernel, which is the engine behind the faster transfer speeds.

Troubleshooting common issues

Phone not detected

• Make sure the phone is unlocked and the USB notification is set to File transfer, not "Charging only."
• Try a different USB cable — charge-only cables won't carry data.
• Reconnect the cable and reopen OpenMTP.

On macOS 10.13 or earlier

• Standard builds won't work. Use v3.1.15 and enable Legacy MTP mode during setup.

Transfer feels slow or stalls

• Close other apps using the device, and avoid transferring while the phone screen is locked.

Is OpenMTP the right choice for you?

Choose OpenMTP if you want a free, open-source, plug-and-play USB transfer tool for macOS that supports renaming, SD card switching, and large files. Consider the built-in Android File Transfer only if you need Apple's first-party utility and can live without renaming on the device. For older Macs (10.13 and earlier), plan on the legacy v3.1.15 build rather than the current release.

Use resizeappicon.com to turn one source image into every icon size iOS, iPad, Apple Watch, and Android require. Upload or drag and drop your original image, and the service generates all resolutions automatically. For the sharpest results, start with a 512x512 or 1024x1024 pixel source image.

What you need before starting

• A source image at 512x512 or 1024x1024 pixels. The site states these resolutions give the best results.
• A browser. This is a web-based service, so there is nothing to install.
• Your target platforms in mind: iOS (iPhone/iPad), iOS Watch, and Android.

Step-by-step: generate all icon sizes

1. Upload your source image

Drag and drop the original image onto the upload area, or upload it manually. The image is uploaded and the icons are generated automatically.

2. Optionally enable instant download

Activate the instant download option if you want to download all icons directly after generation, instead of picking sizes first.

3. Review the generated sizes by platform

The service groups output by platform so you can confirm coverage before downloading.

iOS — iPhone/iPad

iOS — Watch

48, 55, 80, 88, 172, 196 pixels.

Android

4. Download

Use Download all to get every generated icon at once, or Download selected if you only need specific sizes or platforms. The instant download option skips this selection step entirely.

Common problems and how to avoid them

• Blurry or low-quality output. This usually means the source image was smaller than 512x512. Start from 512x512 or 1024x1024.
• Missing a required size. Check the platform tabs (iOS iPhone/iPad, iOS Watch, Android) rather than assuming one download covers everything — each platform has its own size list.
• Downloading one file at a time. Use Download all or enable instant download to avoid saving icons individually.

Managing icons beyond a one-off resize

If you resize icons repeatedly, the site also offers App Icon Management: store unlimited app icons in one place, get notified when new resolutions are required, and have your master icon file maintained for you. This is aimed at teams and client work rather than a single conversion.

The service is built by Beyond Code, the company behind the BotMan chatbot framework, and is made in Germany.