In WordPress, each user can have roles, identifiers, permissions… But not a profile image.
This is a surprising limitation when trying to visually distinguish accounts in the admin area, especially in a structured environment.
The One User Avatar plugin addresses this issue by allowing a custom image to be added to each user profile. While this plugin is no longer included in the default WPDistrib setup, it remains relevant in certain use cases. Here’s what to know before using it in a project.
Understanding Why WordPress Doesn’t Let You Change the Default Avatar
WordPress doesn’t include a built-in system for adding a custom profile image to a user account. The CMS relies solely on Gravatar, an external service that links email addresses to global avatars.
This setup is poorly suited for local, internal, or educational environments, where each user account should have a distinct image without exposing personal data to a third-party platform.
This limitation quickly becomes an issue when trying to differentiate multiple accounts, such as a main administrator, a secondary editor, or a test account. Without visible avatars, all these users appear identical in the admin.
💡 This limitation is structural: WordPress considers the user image as public data, whereas in many cases it should be local and customizable.
Improving Admin Clarity with a Custom Avatar
In a multi-account setup, adding a custom image to each profile offers an immediate boost in clarity. The avatar allows for quick visual identification of the user’s role or purpose.
✅ A theme editing account can be visually distinguished from an admin account.
✅ A test account can have a specific icon to avoid confusion during operations.
✅ In multisite or collaborative contexts, personalized avatars streamline teamwork.
🚀 Example from WPDistrib: a secondary account was used to adjust theme settings, with the User Switching plugin to switch between roles. Thanks to One User Avatar, each role had a clear visual cue, making tests and management more efficient.
Using One User Avatar to Add an Image to a User Account
The One User Avatar plugin solves this simply. It adds an Avatar field to each user profile, letting you assign an image:
👉 Either by uploading a new image.
👉 Or by selecting an existing image from the media library.
👉 Or by leaving the field empty to keep the default avatar.
The image then appears in the admin interface, such as the user list and other screens displaying the author.
✅ No Gravatar account required.
✅ Clean and simple interface that follows native WordPress design.
✅ The image is stored locally on the WordPress site.
💡 This is a lightweight yet helpful feature, especially in training or workshop settings where multiple users need to be clearly identified.
Reassessing Its Role After WPDistrib’s Simplification
WPDistrib recently removed several secondary plugins, including Members and User Switching, as part of an effort to simplify the core distribution. This move reflects a focus on keeping only the essentials.
In this context, One User Avatar was also removed. It is no longer included by default because:
⚠ It is not essential for single-user sites or simple setups.
⚠ It becomes redundant if no real multi-account use case exists.
⚠ It should only be activated when visual distinction between users is needed.
🚫 The plugin is no longer part of WPDistrib by default, but that doesn’t mean it is discouraged.
🌀 One User Avatar: an Optional Plugin to Personalize User Accounts
One User Avatar is not a critical plugin, but it remains recommended in several scenarios:
👉 Educational projects with different accounts for various roles.
👉 Collaborative or multisite setups with multiple authors or moderators.
👉 Local testing cases where a visual marker helps avoid mistakes.
It integrates easily into a WPDistrib site without disrupting visual coherence and adds no technical bloat.
✅ No impact on performance.
✅ Simple, localized, and effective feature.
In conclusion, One User Avatar is a useful plugin worth knowing, addressing a structural gap in WordPress. It can be installed based on project needs, but is no longer part of WPDistrib’s core setup for the sake of simplicity.