Skip to main content
February 6, 2025
Question

Birthdate Format Incorrect

  • February 6, 2025
  • 27 replies
  • 416 views

Hi, I have been having issues with Birthdate autofill formatting.  I have it entered in my profile as mm/dd/yyyy but when I autofill in forms it changes to dd/mm/yyyy (Chrome Ext).

Also I notice viewing profile it displays as m/dd/yyyy

Any fixes?

27 replies

January 3, 2025

when i auto-fill in a field with my birthday it'll do dd/mm/yyyy instead of mm/dd/yyyy

i checked that my birthday is correct in my identity card in 1Pass


1Password Version: 8.10.56
Extension Version: 8.10.56.28
OS Version: MacOS 15.2 (24C101)
Browser: Arc

May 15, 2026

This issue is still happening to me. Seems to happen on most, if not all sites and is happening in both Chrome and Firefox. Any update on the fix? Thanks.

1P_Gem
1Password Employee
1Password Employee
June 5, 2026

Hi @shingy and @gcy, thanks for your replies.

I can definitely see where you're coming from! However, I'm not a dev, so I can't speak to the technical side of things or what's involved in the fix, and I wouldn't want to make any assumptions there.

I'm sorry I can't give you a more satisfying answer right now. I appreciate you both taking the time to share your thoughts, and I've noted what you've said in the issue on file.

cyber-bacon
February 6, 2025

It could be that the extension is pulling from your Language and Region settings in General > Language & Region.

 

February 6, 2025

Just checked and mine is set to basically the same as yours. Thanks though!

kevin_li
1Password Employee
1Password Employee
February 6, 2025

Hey @Steamboater

May I confirm the website that you have the date format input incorrectly to test? 

If the website is not publicly accessible, can you inspect the date input field, and check to see if the input type is "date" rather than "text"?

I can confirm if the input type="text", it will lead to the date format issue you mentioned. Here is a demo screenshot: 

-Kevin

May 15, 2026

(Posting this here as well in case this is logged as seperate tickets)

This issue is still happening to me. Seems to happen on most, if not all sites and is happening in both Chrome and Firefox. Any update on the fix? Thanks.