Can I set a profile picture for my inbox?
AgentMail does not currently have an API field for setting the picture shown beside your emails in a recipient’s inbox. The recipient’s email provider controls that image. Setting an inbox’s display_name changes the sender’s name, and storing an image URL in metadata does not set a recipient’s avatar.
Two separate systems can supply a sender image:
Associate a Google profile picture with your address
You can create a Google account using an existing email address, including an @agentmail.to address or an inbox on your custom domain:
- Open Google’s account creation instructions and choose Use your existing email during signup.
- Enter your AgentMail inbox address and verify it using the code delivered to that inbox.
- Open your Google account’s Personal info, select Profile picture, and upload your image.
- Review your photo’s visibility settings.
This creates a Google account associated with your address. Your email remains hosted by AgentMail; you do not need to move it to Gmail or change your MX records. Google hosts the profile image, and no BIMI certificate is required.
This configures a Google profile photo, not a universal email avatar. It does not guarantee that Gmail will display the photo on messages sent through AgentMail, or that other email providers will use it. Google notes that profile photo changes can take time to appear across its products.
See Google’s profile picture guide for the current steps and display behavior.
How BIMI differs
Brand Indicators for Message Identification (BIMI) lets a domain publish a brand logo for supporting email providers to display. A default BIMI record applies to the sending domain rather than an individual inbox.
For Gmail, the setup includes enforced DMARC, a qualifying SVG logo, HTTPS hosting, and a certificate issued for the logo and domain. The certificate is evidence supporting use of the logo; it is separate from the profile picture you upload to a Google account.
A CMC still requires certification. Uploading an arbitrary image does not automatically make it eligible. Follow Google’s BIMI setup guide for current certificate and image requirements.
Where does the BIMI logo live?
You host the public SVG and certificate on an HTTPS server, such as your website or a CDN. A DNS TXT record points to those assets:
The receiving provider retrieves and evaluates the assets. Gmail can also use the logo embedded in the certificate. Use the domain in the visible sender address for the BIMI record, not the bounce-address domain. For domain setup, see Custom domains.
You need control of the domain’s DNS to publish these records. Customers using shared @agentmail.to addresses cannot publish their own BIMI records on that domain.
Can each inbox have a different BIMI logo?
BIMI supports selectors for different logos on one domain, but each logo needs its own DNS configuration and, where required, certificate. A selector header alone does not make a picture appear. AgentMail does not currently offer managed per-inbox BIMI avatar setup; recipient display and selector handling must be verified with the receiving provider. See the BIMI Group’s selector guide.
Check whether the image appears
After configuring a Google profile, send a test message to a Gmail account and inspect the sender image there. Check that you configured the exact sending address, review photo visibility, and allow time for Google’s changes to propagate. A recipient’s saved contact photo can make the result ambiguous.