You can currently set multiple stroke colours to an object, but they will share the same properties (thickness, position, etc.).
My idea is that you should be able to set all stroke properties on each stroke:
Make sense or am I missing something?
Multiple independent strokes
Loving this suggestion — having multiple independent strokes would give creators way more flexibility without complicating the workflow. Clear, intuitive features like this make a huge difference in day-to-day use, just like how LocateParcels focuses on keeping tracking updates straightforward and easy to follow for users.
I’ll sign for this each and every day.
By-passing this missing feature is such a pain in the bloop.
Still can't believe we're using inner shadow hacks for something as simple as a bottom border in 2026. This would save so much time and keep our layers panel way cleaner. Huge +1 from me - this really needs to be a native feature!
this needs to be added imo, one of the most useful wanted features
+1 FIGMA ADD THISSS ITS NEEDED IT NEEDS TO BE DONE NOT GLASS EFFECT WE NEED THIS RAHHHHHHH
+1000 up votes!!! I can’t believe this is STILL not a feature or implemented functionality in Figma 4 years later. The work around is to enclose the first frame/auto-layout inside another frame---so counter-productive. Please consider adding this in a future release. Please!
how the hell after 5 years we not get obvious function like this, HOW?????
FIGMA, WHY ARE YOU SELLING
can we add this please
#addmultiplestrokes
This is a very basic necessity.
Hey All, thanks for your continued feedback and patience!
We hear you and want to be transparent about this. Independent per-stroke properties have been prototyped by our vectors team this year; from UI, data model, and the file migration it needs. That work is paused right now, so we don't have an exact date or timeline to provide.
Rest-assured that this is on our team’s radar for implementation, so when/if the status changes, I’ll be sure to update this topic. One thing that may help the team prioritize: would the ability to set two strokes help unblock your work, or do you need many? That's currently an open question internally, so your input will carry weight.
Hey All, thanks for your continued feedback and patience!
We hear you and want to be transparent about this. Independent per-stroke properties have been prototyped by our vectors team this year; from UI, data model, and the file migration it needs. That work is paused right now, so we don't have an exact date or timeline to provide.
Rest-assured that this is on our team’s radar for implementation, so when/if the status changes, I’ll be sure to update this topic. One thing that may help the team prioritize: would the ability to set two strokes help unblock your work, or do you need many? That's currently an open question internally, so your input will carry weight.
I always thought there’s no difference between just two and many programmatically 😅 So, I for one would like many if that’s possible but two is still more than one if many is not possible.
Hey All, thanks for your continued feedback and patience!
We hear you and want to be transparent about this. Independent per-stroke properties have been prototyped by our vectors team this year; from UI, data model, and the file migration it needs. That work is paused right now, so we don't have an exact date or timeline to provide.
Rest-assured that this is on our team’s radar for implementation, so when/if the status changes, I’ll be sure to update this topic. One thing that may help the team prioritize: would the ability to set two strokes help unblock your work, or do you need many? That's currently an open question internally, so your input will carry weight.
I find myself needing 2 often in the shape of an internal and external stroke at the same time. Many is not necessary for me
Hey All, thanks for your continued feedback and patience!
We hear you and want to be transparent about this. Independent per-stroke properties have been prototyped by our vectors team this year; from UI, data model, and the file migration it needs. That work is paused right now, so we don't have an exact date or timeline to provide.
Rest-assured that this is on our team’s radar for implementation, so when/if the status changes, I’ll be sure to update this topic. One thing that may help the team prioritize: would the ability to set two strokes help unblock your work, or do you need many? That's currently an open question internally, so your input will carry weight.
Two would absolutely help. Being able to set one inside and one outside on the same layer is the reason I want this.
Two would make me very happy in the short term!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.