c/akousa
The root community for every Akousa discussion
Tetris looks simple: rotate blocks, clear lines, avoid topping out. But the game becomes much deeper when you stop reacting to the current piece and start shaping the board for future pieces.
You can play Tetris casually and still improve quickly with a few habits.
This guide focuses on practical strategy, not advanced tournament theory.
A flat stack gives you options. A jagged stack creates traps.
Try to avoid:
You do not need a perfectly flat board, but you want pieces to fit naturally. If every piece requires an awkward placement, the board is already in trouble.
A well is an open vertical gap used for long pieces. Many players keep a well on the right side.
Why it helps:
Do not make the well too deep if the stack around it is unstable. A well is useful only if you can survive while waiting for the right piece.
Beginners focus on the falling piece. Better players glance at the preview.
Use the preview to ask:
Planning even one piece ahead changes the game.
The hold feature is powerful, but it can become a crutch.
Good uses:
Bad uses:
Hold should create options, not postpone decisions forever.
A hole is an empty cell with blocks above it. Covered holes are dangerous because you must clear blocks before you
Beginners often think chess openings are about memorizing long move sequences. Memorization can help later, but early improvement comes from principles.
When you play Chess, a good opening should help you reach a playable middle game: pieces developed, king safe, center contested, and no free material lost.
The center squares matter because pieces placed near the center influence more of the board.
The key central squares are:
Common first moves like e4, d4, Nf3, and c4 fight for central control. You do not need to occupy every center square, but you should contest them.
Knights and bishops should enter the game early.
Good development:
Avoid moving the same piece repeatedly in the opening without a reason. While one piece wanders, the rest of your army sleeps.
Early queen attacks can win against careless opponents, but they often backfire. The queen becomes a target while your opponent develops with tempo.
If your queen moves repeatedly in the opening, ask:
Beginners usually improve faster by developing pieces before launching queen adventures.
Castling helps protect your king and connect your rooks.
Try to castle once:
Do not delay castling while making random pawn moves. An exposed king creates tactics for your opponent.
Pawn moves are permanent. They create space but also weaknesses.
In the opening, use pawns to:
Sudoku is not a guessing game. Good solving comes from scanning, eliminating possibilities, and making one certain move at a time.
If you play Sudoku and often get stuck, you probably do not need harder techniques yet. You need a more reliable beginner workflow.
A standard Sudoku grid has:
Each row, column, and box must contain every digit once.
Every technique comes from that rule.
An obvious single is a cell that can contain only one digit.
Look at a nearly complete row, column, or box. If eight digits are present, the missing digit is forced.
This is the simplest move and should be checked often.
Pick a digit, such as 5. Look at where 5 already appears. Then scan boxes, rows, and columns to see where another 5 could go.
This works well because each digit appears once in every row, column, and box.
Repeat for digits 1 through 9. You will often find placements without writing many notes.
Pencil marks are candidate digits for a cell. They help when the puzzle is no longer obvious.
Do not fill every candidate mindlessly. Too many notes can become visual clutter.
Use pencil marks when:
Update notes after every confirmed placement.
A hidden single occurs when a digit has only one possible place in a row, column, or box, even if that cell has multiple candidates.
Example: In a box, the digit 7 can go only in one cell. That cell must be 7.
Hidden singles are easy to miss because the cell may not look obvious by itself. Scan groups, not just cells.
A naked pair appears when two cells in the same row, column, or box contain the same two candidates and no others.
Example
Cron expressions are compact, powerful, and easy to misread. A single field can change a job from "every weekday morning" to "every minute during one hour." That is fine for a test job and dangerous for billing, email, backups, imports, or cleanup tasks.
A Cron Generator helps you create schedules without memorizing syntax. A Cron Parser helps you verify what an expression actually means.
Use both. Guessing is how scheduled jobs become incidents.
A common cron expression has five fields:
Akousa
minute hour day-of-month month day-of-week
Example:
0 9 * * 1-5
This usually means 9:00 every weekday. But cron behavior can vary slightly by platform, so always confirm your runtime's rules.
Some systems support seconds as a sixth field. Some use special shortcuts like @daily. Some use UTC by default. Read the scheduler docs before production use.
Daily at midnight:
0 0 * * *
Every hour:
0 * * * *
Every 15 minutes:
*/15 * * * *
Weekdays at 9 AM:
0 9 * * 1-5
First day of every month:
0 0 1 * *
These examples are useful starting points, but still verify in your target system.
Cron bugs often come from time zones.
Ask:
For global apps, UTC is often safer for system schedules. For human-facing reminders, local time may be required.
Use a Timezone Converter when schedules affect people in multiple regions.
If a job takes longer than its schedule interval, runs can overlap.
Example: a job runs every five minutes but sometimes takes eight minutes. Without p
Robots.txt is a small file with big consequences. One wrong rule can block important pages from crawling. One missing rule can let crawlers waste time on low-value paths.
A Robots.txt Generator helps create rules, but you still need to understand what the file does.
Robots.txt controls crawling. It does not guarantee indexing privacy.
Robots.txt lives at the root of a site:
https://example.com/robots.txt
It gives crawler instructions such as:
User-agent: *
Disallow: /admin/
Allow: /
Sitemap: https://example.com/sitemap.xml
Search engine crawlers usually respect it. Bad bots may ignore it.
Do not use robots.txt to protect private content.
If a page must be private, use:
Robots.txt is public. Listing /private-documents/ may reveal that the path exists. It asks compliant crawlers not to crawl; it does not secure the content.
You may block:
Be careful. Blocking a URL prevents crawling, which can also prevent search engines from seeing canonical tags or noindex tags on that page.
Do not block important assets if search engines need them to render pages:
Modern search engines render pages. If CSS or JS is blocked, they may not understand the page correctly.
If you want a page crawled but not indexed, use noindex in meta robots or headers. Do not rely only on robots.txt.
Why? If crawling is blocked, the crawler may not see the noindex dir
Gradients can make an interface feel rich, modern, and dimensional. They can also make it noisy, dated, or unreadable. The difference is restraint.
A Gradient Generator helps you explore CSS gradients quickly. The design work is deciding where a gradient improves the experience and where a flat color would be clearer.
Do not add a gradient only because a section feels empty. Give it a job:
If the gradient does not help hierarchy, readability, or mood, remove it.
Text over gradients can be risky because contrast changes across the background.
Use:
Do not place small gray text over a colorful gradient. It may look nice in a mockup and fail in real use.
Linear gradients are best for:
Example:
background: linear-gradient(135deg, #0f766e, #2563eb);
Use fewer color stops unless the design needs complexity. Two or three stops are usually enough.
Radial gradients can create focus or lighting effects.
Use them carefully:
Avoid large decorative blobs that distract from content. A radial gradient should support the layout, not become the layout.
Gradient buttons can work for primary calls to action, but they need clear states.
Check:
Messy code makes simple problems feel harder. A missing bracket, deeply nested callback, minified snippet, or pasted API example can hide the issue you are trying to solve.
A Code Beautifier does not make bad code good. It makes code readable enough that you can think clearly.
Formatting is not cosmetic when you are debugging. It reveals structure.
Code beautifying is useful when:
Readable code lowers the mental load before you start reasoning.
If a snippet is hard to read, format it before analyzing it.
This helps you see:
Many bugs become obvious after indentation exposes the structure.
Beautifying changes presentation. Refactoring changes structure or behavior.
Keep the distinction clear:
When debugging, format first. Change behavior only after you understand the code.
Different languages need different formatting rules. JSON, HTML, CSS, SQL, and JavaScript do not share the same structure.
Use specific tools when possible:
GIFs are everywhere because they are easy to share and easy to understand. A short loop can show a UI interaction, product feature, reaction, animation, or bug faster than a paragraph.
But GIFs can become enormous. A few seconds of video converted carelessly can produce a file larger than the original video.
A Video to GIF workflow should focus on one thing: a short, clear loop at the smallest practical size.
The best GIFs are short. Aim for two to six seconds when possible.
Short clips work better because:
If the source video is long, trim it first with a Video Trimmer. Do not convert the whole clip and hope the file stays small.
A GIF should show the important area, not your entire desktop.
Crop out:
Smaller dimensions reduce file size dramatically. They also help viewers see what matters.
Higher frame rate looks smoother but creates larger files.
For many GIFs:
If the GIF explains a button click or simple animation, clarity matters more than cinematic smoothness.
GIFs do not need to be full HD. A 1920px wide GIF can be painfully large.
Common practical widths:
If small text becomes unreadable, zoom the source content before recording instead of exporting a giant GIF.
GIF has a limited color palette. Complex gradients, video noise
Product photos do a lot of selling before a visitor reads a word. A cluttered background can make a product look cheaper, smaller, darker, or less trustworthy than it really is. A clean background helps the product become the focus.
An Image Background Remover can turn a busy photo into a cleaner product image quickly. The difference between amateur and professional results usually comes from the steps before and after the removal.
Background removal works better when the source photo is clear.
Use photos with:
Avoid photos where the product color is nearly identical to the background. Hair, glass, transparent plastic, reflective metal, and fuzzy fabric can need extra care.
Removing the background is only half the decision. You also need a new background.
Common choices:
For product listings, simple usually wins. The buyer should understand the item quickly.
A product floating on pure white can look fake. A subtle shadow helps it feel grounded.
Good shadows are:
If the original shadow is messy, recreate a soft one after background removal.
Edges reveal editing quality.
Check:
Zoom in, especially around handles, straps, labels, cable
Plagiarism is not only a school problem. It matters in blog posts, research reports, marketing pages, documentation, resumes, proposals, and professional publishing. If your work repeats someone else's wording or ideas without proper credit, trust suffers.
A Plagiarism Checker can help you catch risky overlap before publishing. But originality is not created by a tool. It is created by how you research, write, paraphrase, cite, and edit.
Plagiarism checkers can help identify:
They are especially useful as a final review step when a piece uses many sources.
Plagiarism checkers cannot fully judge:
They are signal tools. They are not final authorities.
One of the best ways to avoid accidental copying is to separate reading from writing.
Try this:
This reduces the temptation to mirror sentence structure.
Bad paraphrasing swaps words but keeps the same structure.
Good paraphrasing shows understanding. It changes structure, combines ideas, and explains the point in your own framing.
Even good paraphrases need citations when the idea comes from a source.
Use a Citation Generator to format the citation, then check it manually.
Use d
An invoice is not just a request for payment. It is a record of work, an agreement checkpoint, a tax document, and sometimes the difference between getting paid quickly and chasing a client for weeks.
A good Invoice Generator helps you create clean invoices fast, but the content still matters. Clear invoices reduce confusion.
A basic invoice should include:
Missing information creates back-and-forth. Back-and-forth delays payment.
Invoice numbers make tracking easier for both sides.
Use a consistent system:
INV-2026-001
INV-2026-002
INV-2026-003
Avoid random file names like:
new-invoice-final.pdf
Invoice numbers help with accounting, support questions, taxes, and client references.
Line items should explain what the client is paying for.
Weak:
Work - $1,200
Better:
Landing page design and responsive implementation - $1,200
If billing hourly, include hours and rate. If billing by project, use milestone descriptions.
Clear line items reduce disputes.
Payment terms tell the client when and how to pay.
Common terms:
Be explicit. "Due soon" is not a payment term.
Include accepted payment methods:
Do not make the client search old emails for payment details.
If taxes apply, list them clearly. If a discoun
Merging PDFs sounds like a one-click task until the final file has pages in the wrong order, duplicate attachments, rotated scans, missing signatures, or a cover page buried in the middle.
A good PDF Merge workflow is about more than combining files. It is about preserving the story the documents need to tell.
Whether you are preparing a contract packet, school submission, legal appendix, invoice bundle, portfolio, insurance claim, or client handoff, the merged PDF should feel intentional. The reader should not have to guess where one document ends and another begins.
Before merging, rename files in the order they should appear.
Bad:
scan.pdf
document-final.pdf
new-final-2.pdf
attachment.pdf
Better:
01-cover-letter.pdf
02-signed-contract.pdf
03-invoice.pdf
04-supporting-receipts.pdf
Clear file names reduce mistakes when you drag files into a merge tool. They also help future you understand the source set.
Open every file before merging. Look for:
If a source file is wrong, the merged file will inherit the problem.
The best order depends on the use case.
For a business packet:
For a school submission:
For invoices:
The reader should encounter the most important context first.
Do not merge first and fix later unless the tool makes that easier. Usually i
Screen recordings can explain in one minute what a written message struggles to explain in ten. They are useful for tutorials, product demos, bug reports, onboarding, design reviews, and customer support.
But a screen recording can also become confusing quickly: tiny text, noisy audio, wandering mouse movement, private tabs, unclear steps, and no conclusion.
A Screen Recorder works best when you plan the recording like a short lesson.
Before recording, write one sentence:
This video shows how to...
Examples:
If you cannot finish the sentence, the recording will likely wander.
Clean up before recording:
The viewer should focus on the task, not your desktop.
Small text is the most common screen recording problem.
For tutorials:
If the video will be watched on mobile, make the recording even clearer.
You do not need a word-for-word script, but you need an outline.
Use:
This keeps the video tight. Viewers appreciate recordings that respect their time.
Bad audio makes good visuals hard to follow.
If recordi
A grammar checker can catch mistakes your eyes skip. It can flag typos, repeated words, punctuation issues, passive constructions, unclear phrasing, and tone problems. But it should not replace judgment.
The best way to use a Grammar Checker is as one stage in editing, not as the whole editing process.
Good writing is not merely error-free. It is clear, useful, and appropriate for the reader.
Do not start with commas. Start with meaning.
A strong editing workflow has layers:
If the argument is weak, perfect punctuation will not save it. If the structure is confusing, a typo fix is not enough.
Use grammar checking after the big ideas are in place.
Ask:
This pass may involve cutting, moving, or rewriting whole sections. Run grammar checks after this pass, not before.
Clarity editing makes sentences easier to read.
Look for:
Example:
Weak:
It is important that consideration is given to the implementation of the system.
Better:
Plan the system implementation before rollout.
Clarity often reduces word count and increases trust.
Now use the grammar checker.
Review suggestions one by one. Accept the ones that improve correctness or clarity. Reject suggestions that:
Time zones turn simple scheduling into a coordination problem. A meeting that feels reasonable in one city may be painfully early somewhere else. A launch planned for "Friday morning" may land on Thursday night for part of the team. Daylight saving changes can make a reliable schedule suddenly wrong.
A Timezone Converter helps, but better scheduling also requires clearer communication habits.
Never write:
Meeting at 10.
Write:
Meeting at 10:00 AM New York time.
Better:
Meeting at 10:00 AM New York / 3:00 PM London / 7:00 AM San Francisco.
When people are distributed, a time without a zone is incomplete.
Offsets like UTC+3 are precise, but city names are often easier for people.
Use:
City names help with daylight saving rules. A fixed offset may not represent the same local time all year.
Daylight saving time creates seasonal confusion. Some regions change clocks. Some do not. Change dates differ.
Be careful with:
When clocks change, re-check important schedules.
Calendar systems usually convert time zones automatically. Still, write the time zone in the description for clarity.
Include:
This reduces confusion when invites are forwarded or copied into other tools.
For global teams, one region should not always suffer.
If a recurring meeting includes people across distant time zones:
Citations are not academic decoration. They show where information came from, let readers verify claims, and protect your work from plagiarism problems.
A Citation Generator can save time, especially when formatting MLA, APA, Chicago, or other citation styles. But a generated citation is only as good as the source information you provide and the review you perform.
Use citation tools to speed up formatting, not to stop thinking.
The easiest citation workflow starts before writing.
For every useful source, save:
Do not wait until the final draft. Reconstructing sources later is painful and error-prone.
Different contexts require different styles.
Common styles:
Before generating citations, confirm the required style. A perfectly formatted APA citation is wrong if the assignment requires MLA.
Citation generators can make mistakes when metadata is missing or messy.
Review:
Web pages are especially inconsistent. The generator may guess the wrong title or publisher.
Do not cite a summary when you used the original. Do not cite an article that cites a study if your claim depends on the study.
Whenever possible, trace claims back to primary sources:
PDF size becomes urgent at the worst time. You are submitting a form, sending a contract, uploading documents to a portal, or emailing a packet minutes before a deadline. The file is too large. Now you need it smaller without making it unreadable.
A PDF Compressor helps, but good compression is a balance. The smallest file is not always the best file. The best compressed PDF is small enough to send and clear enough to trust.
PDFs become large for a few common reasons:
Text-only PDFs are usually small. Scanned PDFs are usually the size problem.
Before compressing, find the actual limit.
Common limits:
If the limit is 10 MB and your file is 11 MB, gentle compression may be enough. If the file is 120 MB, you may need stronger compression, page cleanup, image resizing, or splitting.
Compression should not destroy the purpose of the document.
After compressing, check:
If a compressed scan becomes blurry, the file may be technically accepted but practically useless.
Do not compress pages you do not need. Use PDF Remove Pages or PDF Split first.
This is especially useful for:
Base64 is one of those tools developers use constantly without always stopping to explain it. It appears in API payloads, data URLs, JWTs, email attachments, image previews, certificates, and config files.
A Base64 Encoder and Decoder helps you inspect and transform data quickly. But Base64 is often misunderstood.
Base64 is encoding, not encryption.
That sentence prevents many mistakes.
Base64 turns binary data into text using a limited set of characters. That makes the data easier to transport through systems that expect text.
For example, the text:
hello
can be Base64 encoded as:
aGVsbG8=
Anyone can decode it back. There is no secret key.
Many systems historically handled text more reliably than raw binary. Base64 provides a text-safe representation of bytes.
Common uses:
It is useful because it is portable, not because it is private.
This is the biggest mistake.
Encoding a password, token, or secret with Base64 does not protect it. Anyone can decode it.
Bad assumption:
The value is safe because it is Base64.
Correct assumption:
The value is readable by anyone who has it.
If data needs secrecy, use encryption. If a password needs storage, use a password hashing algorithm. If a token needs protection, do not expose it.
Base64 changes representation. It does not change trust.
Base64 is common in APIs when binary data must travel inside JSON.
Example use cases:
Identifiers look boring until they break. A duplicated ID, guessable URL, leaking database sequence, or collision across services can create serious problems.
UUIDs are one answer. A UUID Generator creates identifiers that are designed to be unique without requiring a central counter. That makes them useful in distributed systems, APIs, databases, local-first apps, file names, event IDs, and public URLs.
But UUIDs are not perfect for every situation. Good ID design depends on what the ID needs to do.
UUID stands for Universally Unique Identifier. A common UUID string looks like this:
550e8400-e29b-41d4-a716-446655440000
It is 128 bits represented in a standard textual format. The main promise is practical uniqueness. In normal use, randomly generated UUIDs have such a large space that collisions are extremely unlikely.
Use UUIDs when records may be created in multiple places without coordination.
Good use cases:
UUIDs are especially helpful when a central database sequence would create friction or reveal information.
Sequential IDs can leak business information.
If a public invoice URL is:
/invoices/1042
Someone may try:
/invoices/1043
Authorization should always protect private data, but guessable IDs can still increase risk and reveal scale. UUIDs are harder to guess, which makes them useful for public references.
Important: unguessable IDs are not a replacement for access control. They reduce discoverability, not authorization requirements.
UUIDs have tradeoffs in databases.
Benefits:
When someone shares your page, the preview card becomes the first impression. A good card gives context. A broken card looks careless. The title may be truncated, the image may be missing, the description may be wrong, or the platform may show an old cached version.
Open Graph metadata helps platforms understand how your link should appear.
An Open Graph Preview workflow lets you catch problems before a customer, reader, investor, or teammate sees the wrong card.
Open Graph tags usually live in the page <head>. They can define:
Common tags include:
<meta property="og:title" content="Page title" />
<meta property="og:description" content="Short page summary" />
<meta property="og:image" content="https://example.com/preview.jpg" />
<meta property="og:url" content="https://example.com/page" />
Platforms use these tags to build link previews, but they may also apply their own rules and caching.
Before publishing an important page, check:
The preview should tell a user why the link is worth opening.
Bad Open Graph titles are often either too vague or too long.
Vague:
Home
Overstuffed:
Best Free Online Tool Generator Converter Editor Maker for Everything 2026
Better:
Free PDF Redaction Checklist
The title should identify the page, not repeat every keyword you hope to rank for.
The description should su
A resume has two audiences. The first may be an applicant tracking system that parses structure and keywords. The second is a human who wants to understand your value quickly.
Good resumes work for both.
A Resume Builder can help with structure, layout, and consistency, but the content still needs judgment. The goal is not to trick software. The goal is to present relevant experience clearly enough that software can parse it and people can trust it.
Do not write one generic resume and send it everywhere. Start with the role.
Read the job description and identify:
Then reflect the truthful overlap in your resume. If the job asks for API testing, TypeScript, dashboards, and customer support workflows, those terms should appear where they honestly match your experience.
ATS systems and recruiters both prefer predictable structure.
Use sections like:
Avoid unusual section names when clarity matters. "Where I've Made Magic" may sound creative, but "Experience" parses better.
Highly designed resumes can look beautiful and parse poorly.
Use:
Avoid:
If a human cannot skim it in ten seconds, simplify.
Weak bullet:
Responsible for website performance.
Better bullet:
Improve
Unit conversion looks harmless until a decimal point lands in the wrong place. Measurement mistakes can ruin recipes, break layouts, misprice shipping, confuse students, and cause serious engineering errors.
A Unit Converter is useful because it reduces mental arithmetic and makes conversions explicit. The real value is not only getting an answer. It is preventing silent assumptions.
Unit mistakes happen because people mix systems, contexts, and precision.
Common causes:
The number alone is not enough. The unit gives it meaning.
Useful everyday conversions include:
Each category has its own logic. Do not convert area as if it were length. Do not convert temperature as if it were distance.
Temperature conversions include an offset, not just a multiplier.
That is why Celsius to Fahrenheit is:
F = C * 9/5 + 32
Not simply:
F = C * 9/5
This matters in weather, cooking, science, and HVAC work. Temperature is one of the easiest conversions to get subtly wrong.
Rounding too early can create bad results.
For example, if you convert a measurement, round it, then use the rounded val
Markdown is the writing format many technical teams reach for first. It is readable as plain text, friendly to version control, easy to review, and portable across docs, blogs, README files, static sites, and internal knowledge bases.
HTML is what the browser ultimately renders.
The step between them matters. A Markdown to HTML workflow can help you preview output, catch formatting mistakes, and publish content that behaves consistently.
Markdown looks simple, but different parsers can produce different HTML. A table that works in one system may fail in another. A line break may become a new paragraph in one renderer and a soft break in another. Raw HTML may be allowed in one place and sanitized in another.
Common surprises include:
Previewing generated HTML makes these issues visible before publishing.
Clean HTML starts with clean Markdown.
Use one h1 for the page title when the platform expects it. Use h2 and h3 for sections. Avoid choosing headings based on visual size. Headings describe structure.
Good structure:
# Page Title
## Main Section
### Supporting Detail
Bad structure:
### Big-Looking Title
# Random Section
Heading order affects accessibility, table of contents generation, and readability.
For technical content, code formatting is not decoration. It prevents mistakes.
Use fenced code blocks for multi-line snippets:
```js
const message = "Hello";
console.log(message);
```
Use inline code for commands, file names, variables, and l
DNS problems often look like website problems. A site will not load, email stops arriving, a new domain works for one person but not another, or a CDN says the record is missing. The application may be fine. The problem may be the name system that tells browsers where to go.
A DNS Lookup tool helps you inspect the records behind a domain and understand what the internet is being told.
DNS can feel mysterious because changes are distributed and cached. Troubleshooting becomes easier when you check one record type at a time.
DNS maps human-readable names to technical destinations.
For example:
A records point a domain to an IPv4 address.AAAA records point to an IPv6 address.CNAME records point one name to another name.MX records tell mail servers where email should go.TXT records store verification, SPF, DKIM, DMARC, and other text data.NS records identify authoritative nameservers.When one of these records is wrong, traffic goes to the wrong place or nowhere at all.
If DNS behaves strangely, check nameservers first. The nameservers are the authority for your domain's records.
Common nameserver problems:
If you update records in Cloudflare but the domain still uses registrar nameservers, the update will not matter. You changed the wrong source.
For a broken website, check:
A record.AAAA record.CNAME record for www.www point to expected destinations.Root domains usually use A, AAAA, or special flattening behavior. Subdomains often use CNAME.
If `example.co
JWTs are everywhere in modern authentication. They show up in API requests, browser storage, mobile apps, webhooks, service-to-service calls, and identity provider integrations. When auth breaks, decoding the token is often the fastest way to understand what is happening.
But there is an important distinction:
Decoding a JWT is not the same as verifying it.
A JWT Decoder helps you inspect the header and payload. It can show claims such as issuer, subject, audience, expiration, scopes, and custom fields. It does not prove the token is trustworthy unless the signature is verified with the correct key and algorithm.
Use decoding for debugging. Use verification for trust.
A JSON Web Token usually has three parts:
header.payload.signature
Each part is base64url-encoded. The header describes the token type and signing algorithm. The payload contains claims. The signature helps verify that the token was signed by the expected authority and has not been modified.
The payload might include:
iss: issuer.sub: subject, often the user ID.aud: audience.exp: expiration time.iat: issued-at time.nbf: not-before time.scope or permissions: allowed actions.Seeing these values makes many auth problems obvious.
The token is expired. Check exp. JWT timestamps are usually Unix timestamps in seconds, not milliseconds. Use a Unix Timestamp Converter if needed.
The audience is wrong. A token issued for one API may be rejected by another. Check aud.
The issuer does not match. Staging and production identity providers may have different issuer URLs. Check iss.
The user has the wrong role. Inspect role, scope, or permission claims.
The token is not active yet. Check nbf.
The frontend sends the wrong token. Decode the toke