A free stack is a set of limits you accept
You can get real work done without a subscription. You cannot do unlimited work, and you should not plan a client deadline around a free tier that can throttle you at 4 p.m. The point of a free stack is to cover the jobs in a normal week: think something through, check a fact against a link, make a rough image, get unstuck on a small piece of code, and keep notes. Pay when a limit, not a feeling, is what blocks the job.
This is not a promise that any named button will still be free next month. Companies move features between plans. When you rely on a free tier, open the vendor's pricing page the week you start, and again before you promise a client a volume you have not tried.
The chat you keep open
A general chat assistant is the first piece, because it is where drafts and explanations happen. OpenAI, Anthropic, and Google each offer a way to try their chat products without paying. The model on the free plan may not be the model on the paid plan. That is fine for learning a workflow and for short drafts. It is a bad surprise if you assumed the free window included a tool you saw in a demo.
Use the free chat for:
- Outlines and rewrites of text you paste in.
- Explanations of an error message you also paste in.
- A second version of an email, after you have written the facts yourself.
Do not use it as a search engine. If the answer needs a source, switch tools. Do not paste private client files into a free consumer plan. Read the privacy terms. If the terms are unclear to you, keep the file out.
When the free cap hits, that is information. If it hits once a month, you may not need to pay. If it hits every morning, the paid plan is the cheaper one, because your time is the cost you are already paying. The social media content guide shows where a chat fits in a publishing week so you are not burning the daily cap on tasks a template could do.
A place that shows links
For questions about the world, use a tool that returns links you can open. Perplexity is built that way: the answer is tied to sources, and the free product is enough to learn the habit of clicking them. Other search products, including Google's own AI features in Search, also surface links. The habit matters more than the logo. If you cannot click through to a primary page, you do not have a fact yet.
A good free-stack rule: the chat drafts, the cited search checks. Mixing those jobs in one window is how a made-up date ends up in a caption. The student guide uses the same split for coursework, where the cost of a fake citation is an academic problem, not just an embarrassing edit.
Images without a subscription
Free image tools exist, and they come with visible limits: watermarks, slow queues, small download sizes, or a handful of generations a day. Use them for exploration. A thumbnail concept. A storyboard frame. A background you will replace.
Before you publish, read two pages: the tool's current license, and the rules of the site you are posting to. Some free plans allow personal use and restrict commercial use. Some allow commercial use and restrict training or resale of the model outputs in ways you need to read carefully. "It was free" is not a license.
If you outgrow the queue, compare the three working styles in the image model guide. One of them, running an open model on your own machine, has no monthly fee and a hardware cost instead. That trade only makes sense after you know you generate images often enough to care. The hardware guide is about that cost in gigabytes and memory, not in a shopping ranking.
Code help that does not require a seat
For programming, the free tier of a chat assistant is enough to explain a snippet and to suggest a fix you then test. GitHub also offers Copilot access under terms that depend on whether you are a student, a maintainer of a popular project, or a paying customer. Those programs change. Read GitHub's Copilot docs rather than a blog's memory of who qualifies.
Editor features you do not pay for still demand the same review. Run the code. Read the diff. A free suggestion can break a build as easily as a paid one.
If you want completion inside an editor and you do not want a subscription yet, start with the chat and your normal editor. Move to Copilot or Cursor when the copy-paste between the browser and the editor is the thing wasting your hour. The Cursor and Copilot comparison is about that choice.
Notes, and the tool you already have
The most underrated free tool is the notes app you already open. A model does not need to store your prompts if you store them. Keep a page with three briefs that worked, the voice sample you reuse, and the list of facts a draft is allowed to use. That page makes every free chat smarter without another account.
If you already live in Notion, Google Docs, or a plain folder of Markdown files, do not add a second system because an AI feature exists. Turn the feature on only if it saves a step you can name. Summarizing a meeting note you already pasted is a step. A new inbox of "AI suggestions" is not. The Notion AI review is for people who have already decided the notes live there.
What "no credit card" should mean to you
Prefer tools that let you try the product before a card is stored. If a signup demands a card for a trial, put a reminder on your calendar for the day before it bills, or do not start. Free trials are a pricing tactic. Your calendar is the countermeasure.
Also notice what the free plan is learning. Some products use consumer chats to improve models unless you opt out, and the opt-out may live in settings rather than in the signup flow. If you cannot find the control, do not put anything in the chat you would mind being used as an example. This is not legal advice. It is a reason to read the privacy page of each tool you add to the stack.
A stack you can write on one card
Here is a concrete stack that stays free until a limit forces a decision:
- One chat assistant, free tier, for drafts and explanations of text you provide.
- One cited-search tool, for questions that need a link.
- One image tool, free tier, for concepts you might throw away.
- Your existing editor and notes, with prompts stored by you.
- Optional: a local model later, if privacy or volume, not novelty, is the reason. The beginner guide to running models locally starts at install, not at a parts list.
Write the five lines on a card. When someone recommends a sixth app, ask which line it replaces. If it replaces none, it does not go on the card.
When paying is the honest next step
Pay for the tool whose limit you hit on real work, not for the tool with the loudest launch. A watermark on a client deliverable is a real limit. A daily cap that stops you at the second email may be a real limit. A missing feature you have not needed is not.
Cancel the inverse: anything you have not opened in a month. A free account you forgot is harmless. A paid account you forgot is the expensive kind of stack.
The tool directory and the top tools page are maps. They are not a bill. Start from the card above, and add a name only when a job on the card is failing.