The wonderful company I work for, Payoneer, has a new logo, and my job was to recreate it and animate it for a loader component in our app. I’ll explain exactly how I did it, share the problems I had, and walk you through the solution I came up with. And, as a bonus, we’ll look at animating it!
But first, I guess some of you are asking yourselves… Recreate it? Why?
The branding agency that designed our logo sent us a full set of assets categorized by themes. They came in all sizes and in every available format. We had everything, including SVGs, for the logo and the loader animation. But we couldn’t use them.
Here’s why. Let’s take a look at the logo:
The logo is a ring with a conic gradient that consists of five colors, and… that’s it. The problem is that SVG doesn’t support angled gradients (for now, at least), so when we export a design that has a conic gradient as an SVG, we need some sort of hack to get the desired result.
Now, I’m no expert when it comes to working with vector graphic software, so there might be a different (and perhaps better) way to do this, but I know that the most common way to export conic gradients to SVG is to convert the gradient element to an image and insert that image into the SVG as a base64 string. That’s also what we got from the branding agency, and I trust them to know the best way to export an SVG.
But, since the final SVG file now contains a PNG base64 string, the file size jumped to nearly 1MB, which might not be a total disaster, but it’s much higher than the 2KB that it should be. Multiply that difference by three themes (no text, light text, and dark text variations), and we’re looking at 3MB worth of images instead of 3KB worth of code. That’s a big difference, so we’ve decided to recreate the logo with SVG.
But how?!
Even though CSS fully supports conic gradients, SVG does not. So the first question I asked myself was how to create a conic gradient in SVG. Actually, I asked Google. And what I found was a lot of cool, unique, creative ways to add a conic gradients to SVG, most of them relying on some sort of clip-path
implementation. I first created a short <path>
that represents the shape of the ring and used it as a clip-path
on a simple <rect>
element.
Next, I needed to fill the <rect>
with conic gradients, but first, I had to find all the correct color stops to recreate the look. That took a while, but after a lot of fine tuning, I got a result I’m happy with:
div.gradient {
background-image: conic-gradient(from 270deg, #ff4800 10%, #dfd902 35%, #20dc68, #0092f4, #da54d8 72% 75%, #ff4800 95%);
}
The last step was to replace the <rect>
with something else that supports conic gradients, and the simplest way I’ve found is to use an SVG <foreignObject>
element with a regular <div>
inside it, and a conic-gradient
as a background-image
. Then all I needed to do was to set the clip-path
on the <foreignObject>
element, and that’s it.
So, that’s how I used a conic gradient in an SVG to keep the design fully vector and scalable with less than 20 lines of code, and less than 2KB in file size.
But that was the easy part. Now let’s talk animation.
The loader
Our app shows a loading animation every time a user logs in. We had been using a GIF file for it, but I had been meaning to update it to a pure CSS/SVG animation for months. The benefits are obvious: faster render means a more seamless loading experience, and a smaller file size means even faster loading. We simply get more for less, which is especially ideal for a loading animation.
Here’s the animation I was aiming for:
This type of animation is actually fairly easy with SVG. All we really need is a trick using stroke-dasharray
and stroke-dashoffset
. That was my starting point. I created a new <path>
in the center of the ring, removed the fill
, added a stroke
with the right stroke-width
, and then worked on the animation.
It took me some playing around to get the movement just like the designers wanted it. I ended up using two animations, actually: one controls the stroke-dashoffset
, and the second rotates the entire <path>
a full turn.
But, since the clip-path
property refers to the fill
of the shape, animating the stroke meant I had to solve one of two problems: I could either find a different way to animate the movement, or find a different way to add the colors to the stroke.
So I went back to Google and all of the creative ideas I found before, but most of them were pretty much un-animatable, so I started looking for a good non-clip-path
way to add colors to the stroke. I looked at a few “out-of-the-box” solutions, checked out masking, and ended up with the simplest perfect solution:
.logoBlend {
mix-blend-mode: lighten;
}
A lighten
blend mode looks at the RGB colors of each pixel of the rendered element, compares it to the RGB value of the background pixel that’s behind it, and keeps whichever is highest. That means that the parts of the element that are white will remain white, and the dark parts will get the values of the background pixel.
By adding a white <rect>
to the black path, I essentially blocked anything that’s behind it. Meanwhile, everything that’s behind the animated black stroke is visible. That meant I could bring back the <foreignObject>
with the conic-gradient
, put it behind the mix-blend-mode
layer, and give it a simple rotate animation to match the design.
Note that the end result of this method will have a white background, not transparent like the static logo, but I was fine with that. If you need to, you can flip it around, use black background, and hide the light parts of your element by setting the blend mode to darken
.
Final touches
I was pretty much done at this point, and quite happy with the end result. But a couple of days later, I got a Lottie-based JSON file from the branding agency with the exact same animation. In retrospect, maybe I could spare my work and use their file, it would have worked just fine. Even the file size was surprisingly small, but it was still 8✕ bigger than the SVG, so we ended up using my animation anyway.
But, that meant I had one last thing to do. The Lottie animation had a “start animation” where the small orange dot grows into view, and I had to add it to my animation as well. I added a short 0.5s delay to all three animations as well as a scaling animation in the beginning.
Click on “Rerun” on the Pen to see the animation again from the initial dot.
That’s it! Now my company has a new logo and a set of lightweight, fully scalable assets to use across our web platforms.
And for those of you wondering, yes, I did end up creating a nice little Logo component in React since we’re using it. It even renders the SVG according to a theme passed to it as a prop, making the implementation easier, and keeping all future changes in a single location.
What about you?
Do you think there’s a better way to get the same result? Share your thoughts in the comments! And thank you for reading.
Cool deep-dive! This is interesting stuff.
Not 100% performant on Firefox, but looks smooth on Chrome (and sadly, it has the same issue as your final demo on Safari with the animated stroke, I think): https://codepen.io/chriskirknielsen/pen/vYmKeRW
No blend-mode magic, but using the animated path as a mask instead — but overall adds a few bytes to the mix. I think your version is probably best for now! :)
Hi, thanks!
I’ve tested it again on FF, looks fine on my end. If you had performant problems on FF, please share them with me.
As for issue with the animated stroke on Safari, I’ve fixed it by resetting the animation values:
:)
Yea this perform horribly for me in FF90. Lots of stuttering
Thanks for writing about it.
After I read it, all I could think about: I must try it on one of my websites. I hope it will work properly in all browsers.
I have one problem with it. Most people have a slow computer and it possibly uses too much performance. It will be useful if somebody tests that.
This is a small SVG file with a tiny animation, there is no reason for it to be heavy. The resources it requires are nothing compared to the resources required by libraries like Three.JS or even Lottie.
As for working properly in all browsers, it’s absolutely possible. Just be careful what you use, and do a lot of testing.
The animation you were aiming for has the colors rotating. On Safari at least, yours doesn’t rotate the colors.
Yep, the animation doesn’t work on the foreign object, ease fix, I’ll get to that soon.
Thanks!
Yep, the animation doesn’t work on the foreign object, ease fix, I’ll get to that soon.
Thanks!
wow cool bro..! thanks for this tip
The Codepen examples don’t work in Firefox for Mac (October 2021) if conic gradients are not enabled.
For that one has to open about:config (URL) window and change layout.css.conic-gradient.enabled setting to true.
Is there anyway to get this to work with a transparent background instead of a white one?
Did you find a way to have transparent background?
Can this be used for a favicon?
I’m a CSS enthusiast and complete SVG n00b, so I mostly came here simply to admire someone else’s technical mastery of Web graphics design and coding prowess.
But while reading the article, a very warm and reassuring feeling washed over me, as I realized we’ve finally arrived at a time when developers no longer devote half their creative energies dodging browser-specific landmines!
Remember “Dynamic HTML” and its dreaded work-around tables? Using IE, do this. Using Firefox, do that. Got Opera? Sorry, bro.
So… THANK YOU, HTML5. Thank you, CSS. Thank you Flex, and SVG, and JS, and Google (for Chrome), and PNG (for alpha), and all the rich coding goodness now at our disposal. Seems we can finally just focus on the fun parts.