Where are the old studies/GitHub?
Previously distributed through my GitHub. You can still find the older versions there. Going forward, this site is the only updated and maintained home for all gcUserStudies work, with automatic updates, proper authorization, and more studies on the way.
What is gcUserStudies?
gcUserStudies LLC develops custom trading studies for the Sierra Chart platform. All studies are provided free of charge and sustained through voluntary contributions. They are written in C++ and distributed as DLL files directly through Sierra Chart’s built-in Sierra Chart’s built-in distribution system.
Why do I need to register to access free studies?
The registration requirement is not about making free things difficult; it is how Sierra Chart’s DLL distribution system works. Authorizing your account is what allows studies to automatically update, download and install to your system.
What do I need to use your studies?
Sierra Chart for Windows, version 2813 or higher. Our studies are Windows only (macOS and Linux are not supported). You will also need an active Sierra Chart account.
How do I access studies after signing up?
A couple of things to check before you get started. Log into your Sierra Chart account and confirm that automated downloads are enabled on your account. This is the default setting for most accounts but worth verifying. You should also see gcUserStudies studies listed as authorized on your account page once your membership is active.
Sierra Chart Settings
Custom studies are not available in Safe Mode. You can check this on the Sierra Chart login window.
Finding the studies
After restarting Sierra Chart, go to Analysis > Studies > Add Custom Study. You will see a list of study bundles. If other bundles are expanded, click the minus sign to collapse them. Find the gcUserStudies bundle, click the plus sign to expand it, and you will see the individual studies available to add. A restart of Sierra Chart after authorization is usually all it takes for everything to appear.
Which Sierra Chart username should I use?
Use the exact username on your active Sierra Chart account which is the same one you use to log in. You can confirm it in Sierra Chart under Help > About. If it is entered incorrectly at signup, authorization will fail and studies will not appear. You can check the name entered in your profile under your membership account. If you find you entered it incorrectly, please contact support.
How long until studies appear after signup?
Authorization is typically processed within a few minutes of signup. Once authorized, studies will download the next time Sierra Chart starts. If they do not appear after restarting Sierra Chart, work through the troubleshooting steps below.
The studies are not showing up, what should I check?
- Confirm your Sierra Chart username was entered correctly at signup
- Log into your Sierra Chart account at sierrachart.com and confirm automated downloads are enabled
- Confirm you are not running Sierra Chart in Safe Mode
- Restart Sierra Chart and give it a couple of minutes to sync
- Go to Analysis > Studies > Add Custom Study and look for the gcUserStudies bundle
If you still cannot find them after the above, email [email protected] with your Sierra Chart username and a description of what you are seeing.
Can I use the studies on more than one computer?
Yes, as long as you are logged into the same Sierra Chart account on each machine. Authorization is tied to your Sierra Chart username, not your hardware.
What if I change my Sierra Chart account?
Your current authorization will stop working if your username changes. Email [email protected] with your old and new username and we will update your authorization. Allow up to 24 hours for the change to take effect.
Can I transfer my membership to a different Sierra Chart account?
Yes. Your membership is tied to the Sierra Chart username provided at signup. If you need to move it to a different account please contact us at [email protected] and we will update it. Allow up to 24 hours.
What does access cost?
All studies are free. No credit card required, no expiration. If you find the studies useful and would like to support ongoing development and hosting costs, contributions are welcome here: [Contribute]
Any contribution is a one-time, optional payment, not a subscription. There is no obligation to contribute.
How do I get access?
Sign up for a free account on each study bundle or study’s page. Once registered, your Sierra Chart username is linked and access is granted automatically within a minute. Close and re-open Sierra Chart for the files to download. Already have an account? You can view and sign up for all available studies from our membership levels page.
How do I cancel?
You can cancel your membership for any study at any time from your membership account page. Access is revoked on the next sync.
Do you offer refunds?
If you choose to support the project via a voluntary payment, all payments are final as they are optional contributions, not purchases. If you have a technical issue, contact support before doing anything and we will work to resolve it.
What payment methods do you accept?
Voluntary contributions are processed through Stripe. Supported payment methods are shown at the Stripe Contribute Link.
What is a DLL file?
A DLL (Dynamic Link Library) is a compiled file that Sierra Chart loads as a custom study. Our studies are delivered this way for performance. No programming knowledge required. The DLL downloads and installs automatically through Sierra Chart’s distribution system.
Do I need a compiler or any development tools?
No. Our studies are pre-compiled and delivered automatically through Sierra Chart’s distribution system. Nothing to install, compile, or configure beyond enabling automated downloads in your Sierra Chart account.
Can I see the source code?
All of our studies are closed source. The source code is not provided.
What kind of computer do I need to run these studies?
Trading is a performance-intensive activity. Studies add real-time calculations and rendering on top of Sierra Chart. For the best experience you will want a modern CPU, adequate RAM, and a dedicated GPU if you are running multiple monitors or complex chart layouts. If you notice sluggishness or rendering lag, your system specs may be a factor. As a general rule, if your trading setup handles Sierra Chart comfortably today, these studies should run without issue.
My antivirus flagged your DLL as suspicious. Is it safe?
Yes. Sierra Chart studies are compiled as standard Windows DLLs that use Win32 APIs for keyboard shortcuts, drawing, and window management. Some antivirus engines use AI-based heuristics that occasionally misidentify these API patterns as suspicious. This is a known false positive common across Sierra Chart study developers, not unique to our studies. All major engines (Microsoft Defender, Kaspersky, ESET, Norton, CrowdStrike, Malwarebytes, etc.) report our DLLs as clean.
Do you scan your DLLs before release?
Yes. Every release build is scanned on VirusTotal (70+ antivirus engines) before distribution.
Are you affiliated with Sierra Chart?
No. gcUserStudies LLC is an independent third-party developer. Sierra Chart is its own separate product and company. We develop for the Sierra Chart platform but are not affiliated with or endorsed by them.
How do I get help?
Email [email protected] – we aim to respond within one business day. For the fastest resolution, include your Sierra Chart username and a description of what you’re experiencing.
I have a question that is not answered here.
Use the More Questions? button below to reach us directly. We are happy to help.
Do you take on custom development work?
Sometimes. But I’m selective about the projects I take on. Not because I don’t have the capacity, but because I care about what I contribute to, whether my name is attached to it publicly or not. If you’re considering reaching out, please read this section first.
What will you build?
Tools that do what they say they do. Honest data visualization, legitimate analytical tools, and functionality that helps traders see the market more clearly. If you have a well defined study that needs porting to Sierra Chart, or a custom tool for your own trading, that’s a conversation worth having.
What won’t you build?
Tools designed to overstate an edge, manufacture confidence in unproven signals, or power a service that sells the dream rather than delivers real value. Trading is hard enough without adding even more noise to it.
What if my project involves a signal or alert service?
I require verifiable live out-of-sample performance data before engaging, not backtest results. That means real broker statements across a meaningful sample period, ideally covering multiple market conditions and at minimum one full year of live trading. Three months in a trending market is not an edge. If the results are real, the documentation exists.
What about intellectual property?
If you’re bringing existing code or logic to be ported, you represent that you own it or have the rights to it. I won’t knowingly reproduce another developer’s proprietary work. Filling a functional gap is different from copying someone’s specific implementation. If something already exists and does the job well, my honest advice is to use that first. Whatever I build for you stays with you for your stated use. Redistribution or resale of deliverables requires a separate agreement.
How does intended use affect the project?
For all projects I ask clients to disclose intended use upfront. My rates and terms differ depending on whether a tool is for personal use or commercial deployment.
How do contracts and NDAs work?
All work is scoped and agreed upon in writing before development begins. NDAs are signed by gcUserStudies LLC protecting your proprietary logic. I ask that any NDA be scoped to your specific implementation and not broad enough to prevent independently conceived work in similar categories. Scope creep is billed separately.
Do you provide source code?
No. Deliverables are compiled DLLs. Source code is retained by gcUserStudies LLC. This is standard practice and protects both parties.
Can you publicly reference gcUserStudies as your developer?
Not without written consent.
Still interested?
If everything above aligns with your project, reach out at [email protected] with a brief description of the scope.