August 14, 2026
New to Filestack, 10 Free Resources to Get Started
New developers can get started with Snap, then create a Filestack key and make one upload before opening the deeper references. Every…
By Filestack Insights
4 min read
New developers can get started with Snap, then create a Filestack key and make one upload before opening the deeper references. Every resource below is free, and we checked each link in July 2026. The list follows the order a new developer will need it.
Key takeaways
- Snap lets you test the picker and transformations before creating a Filestack account.
- A free API key appears in the Developer Portal after the first application is created.
- The quick start turns one upload and one transformation into a working baseline.
- The processing reference and SDK docs supply exact task parameters once the baseline works.
- The status page and changelog separate service issues from changes in your own integration.
1. Snap needs no account
Snap is the fastest way to find out whether this fits your project because it runs in demo mode with no credentials. You can configure a file picker, set accepted file types and sources, restyle it, and apply image transformations against a live CDN while watching the result change.
2. A free API key
Create a free account and the key appears in the Developer Portal as soon as your first application exists. There is nothing to install to get one and no card required.
Worth knowing up front: the key is public by design and travels in the URL. It identifies your application, it does not protect it.
3. The quick start
The quick start guide is genuinely quick, and it is HTML first, so you can paste it into a plain file and open it in a browser without a build step. If you have ten minutes and a text editor, this is the ten minutes. Our own walkthrough of getting to a first upload covers the same ground with the responses shown.
Shorter still, if you just want to see the thing work: upload a file and transform it, with two commands and no SDK.
# returns JSON containing the handle
curl -X POST --data-binary @photo.jpg -H "Content-Type: image/jpeg" \
"https://www.filestackapi.com/api/store/S3?key=YOUR_API_KEY"
# the handle identifies the app, so no key from here on
curl -o out.webp \
"https://cdn.filestackcontent.com/resize=width:400/output=format:webp/HANDLE"# returns JSON containing the handle
curl -X POST --data-binary @photo.jpg -H "Content-Type: image/jpeg" \
"https://www.filestackapi.com/api/store/S3?key=YOUR_API_KEY"
# the handle identifies the app, so no key from here on
curl -o out.webp \
"https://cdn.filestackcontent.com/resize=width:400/output=format:webp/HANDLE"Every other transformation is that same URL with a different task name in the middle segment.
4. The processing API reference
The processing API reference is the page to keep open in a second tab permanently. Every transformation is a URL segment, and this lists all of them with their parameters, which means most of your questions are answered by scrolling rather than searching.
Pair it with the image editing api guide, which covers the same operations as prose rather than as a reference.
5. The demos gallery
Filestack's examples show working file uploads, image transformations, and document viewing rather than describing them. This is where to look when you know what you want to build and want to see the shape of it first.
The transformation examples are the useful half. Choosing when to convert to webp and when to leave a file alone is the kind of decision these make concrete.
6. The SDKs
There are official SDKs for JavaScript, React, Python, Ruby, PHP, Java, Go, Android, iOS and Swift, listed on the SDKs page and maintained in the open, with filestack-js on GitHub as the flagship. The JavaScript one is the most complete and the one the picker documentation assumes.
You do not need any of them to start. Uploads and transformations are plain HTTP, so curl works fine on day one.
7. The JavaScript SDK API reference
Generated from the source and published at filestack.github.io/filestack-js, this is the reference for method signatures, picker options, and types. It is a different resource from the docs site and more precise about the things you will actually get wrong, like which picker options exist and what they accept.
8. The YouTube channel
The Filestack YouTube channel is where to go if you would rather watch someone build it than read about it. The Node and Express picker build is the one to start with, and the transformations walkthrough is the one to have running in another window while you write your first URL.
Take the code from the videos and the Developer Portal screens from the docs, since we have redesigned the portal since some of these were recorded.
9. The status page and the changelog
status.filestack.com is where to look before you spend an afternoon debugging your own code, and it is the single most useful bookmark on this list on the day you need it. The changelog covers the other direction, which is what changed and when.
Both matter more once you are in production, where the file delivery path and its caching behaviour are the things you will be reasoning about.
10. The Claude Code plugin
The newest resource here. The Filestack plugin for Claude Code brings the platform into the terminal as MCP tools and skills, so you can upload files, build transformation pipelines, generate signed policies, set up webhooks and debug API errors through conversation.
It is the shortest path from an idea to a working URL if you already work this way, and it is worth installing before you start hand-writing transformation strings.
What to do with all of this
Two hours, in this order, gets you further than a week of reading. Spend twenty minutes in Snap to see whether it fits your project. Use ten minutes on the quick start to upload a file from your own machine. Then spend an hour in the processing reference, changing one task at a time on a URL and watching what comes back.
That leaves the demos gallery and the SDKs for when you know what you are building, and the status page and changelog for when you are running it. Face detection is worth trying early, because blur faces is the operation most people assume they will have to build themselves.
One boundary worth knowing before you plan around it. Of 65 operations tested in July 2026, 50 run on a free key, including everything in the two commands above. Thirteen return a 403 and belong to the higher plans: smart_crop, enhance, upscale, redeye, tags, sfw, caption, ocr, copyright, doc_detection, image_sentiment, text_sentiment, and video_convert. The rule behind the split is easy to hold in your head. If an operation has to understand what is inside a file, it is on a higher plan. If it changes the file's shape, size or format, it is on the free one.
The free plan page maps every capability onto the plan that carries it. Read it once you have run a few operations and know which ones your project leans on, because by then the choice makes itself.
When you are past prototyping, the file delivery workflow guide is the one that covers how these pieces fit together as a workflow rather than as a list of tools.
This article was published on the Filestack blog.