Add URL / URI field to Secure Notes (possibly including favicon, launch, ... functionality)

Situation

  • There are no options to add a clickable URI to a Secure Note item, unlike Login.
  • Similarly, unlike Login type, a Secure Note cannot inherit the favicon from a site

Suggestion

  • Add a URI field in Secure Note type
  • Enable inheriting the favicon from a site if a Secure Note has a URI

Many thanks.

I’m requesting the ability to add a URL field to secure notes. I find that secure note forms best meet my needs for the info I am storing in Bitwarden with the exception of not having a URL field. I can’t be the only one who could use this ability.

Are you familiar with custom fields? They can be used to create a URL field in a secure note. Here’s a tutorial just in case you are not familiar.

Thank you for your reply. I have looked at the tutorial, however, I do not see how this works. I am more of a hardware person than a software person…

When editing a Secure Note look for the link/button that says “New Custom Field” and click it. That will display a new field “Name” and “Value”. In the Name text box you could type “URL” and in the Value text box you could type in https://example.com or whatever URL you are wanting associated with that Secure Note.

The custom vault type feature that is currently being developed will likely provide the functionality that you need.

In the meantime, you can use the work-around suggested by @JeremyCouch (storing the URL in a custom text field), or you can consider storing your secure notes in the “Notes” section of a login item (with a blank username and password) instead of using a Secure Notes item. The advantage of using a Login item to store the URL is that you will be able to use the “Launch” button to open the URL from the Bitwarden app.

Thanks for your quick reply. I have given your suggestion a try. If I click the URL data nothing happens, however, if I click the “copy value” button I can paste it into the browser. Is this how it’s supposed to work?

Thanks for your reply on the project update…

I explained this in my response above. If you store the URL in a custom text field, it is treated as any other text, and cannot be used as a hyperlink.

However, if you start using Login items to hold your secure notes, then you can add a URL to a URI field, which allows you to click the “Launch” button to open the corresponding web page.

Wa this ever implemented?

Here is my use case: I store Bitlocker keys in my Bitwarden as a secure note. I would like to add the URL of my iDRAC so that when we connect to the iDRAC’s web interface, the Bitwarden browser extension will show that we have a save entry for the iDRAC which would be the Bitlocker keys so that way we don’t have to go searching for it.

@Rupak.Sinha I merged your Feature Request (FR) with this one to the same topic.

Note: I updated the title of this Feature Request (FR). Before, it was: “Add feature to allow add of URL to secure note”.

@MFKDGAF As far as I know, if has not been implemented.

Is there any reason why you couldn’t simply store your Bitlocker keys in the Notes field (or even better, in a Hidden custom field) of a Login item?

I could but I prefer not to because then when I go to view my vault it looks like there is a login and password when there isn’t one.

Also, if I go to edit it, there are extra fields that I shouldnt have to see. These extra feilds clutter the view.

I really wish they made it so that you could crerate a secure note type and add these fields as extras with out having to create it as a login type.

FYI, the username, password, and TOTP quick copy icons will be grayed-out if there are no values in those fields:

image

But it seems that you are really looking for something like what is described in this Feature Request:

Off-topic for the thread, but:

Yeah, but as your screenshot shows the three separate copy buttons… maybe not currently “grayed-out”, as there is a “new bug” about that:

I’m still on 2025.3.1 — here’s hoping that 2025.3.3 is released with fixes before my extension is updated to 2025.3.2… :crossed_fingers:

1 Like

Maybe I’ll skip 2025.3.3 because I fear new bugs - and hope for 2025.4.0 to fix them. :laughing: