
How to fix problems with DrawKit
Start with the outage graph above. Asset libraries fail in two different places - browsing and downloading - and only one of them is usually broken at a time.
- Check whether browsing works but downloads fail, or the other way round
- Try a different asset; a single corrupted file is not an outage
- Sign out of DrawKit and sign back in
- Confirm your licence or subscription is still active
- Clear your browser cache and cookies, then open DrawKit again
- Try DrawKit on mobile data instead of Wi-Fi, or the other way round
Frequently asked questions about DrawKit
My download from DrawKit keeps failing. Is that an outage?
Not always. A download that stops at the same point every time points at that one file. Downloads that fail at random points point at DrawKit or at your connection.
Can I still use assets I already downloaded?
Yes. Files already on your machine are unaffected by an outage. Only fetching new ones and anything that checks a licence online will be interrupted.
How do I know if DrawKit is down for everyone?
Look at the outage graph above. A sudden spike in reports means the problem is on the DrawKit side and there is nothing to fix at your end. A flat graph points at something local - your connection, your device, or your account.
DrawKit is down. What can I actually do?
When the reports are widespread, waiting is the honest answer - the library is being restored by people who already know about it. Before you settle in, it is worth checking your internet connection and reloading DrawKit once, because that rules out the handful of causes that look identical from your side.
Why is DrawKit working for other people but not for me?
Outages are often partial. They can hit one region, one platform, or one group of accounts while everything else carries on. Your own connection, an old app version or a cached login can also produce a problem only you can see.

