Chrome Extension Help

Customize websites and automate routine clicks without writing code.

Ladybird is for people who repeat the same web tasks, want cleaner pages, or need faster shortcuts inside websites they use every day.

Quick Start

Follow these four steps the first time you use Ladybird.

If you only remember one workflow, remember this: open the site, open the side panel, add what you need, then save and check the result on the page.

1

Open the webpage you want to change.

Go to the actual page where you want a shortcut button, an automated flow, or a hidden rule. Ladybird works against the page you currently have open.

2

Open the Ladybird side panel.

Use the extension side panel so you can see the tabs for Elements, Flows, Hidden, Overview, and Settings while keeping the page visible beside it.

3

Add an element, a flow, or a hidden rule from the right tab.

Use Elements for things you want to place on the page, Flows for multi-step actions, and Hidden when you simply want something to disappear.

4

Save, then check the page or run the flow.

After saving, your new UI should appear on the page, your hidden rule should take effect, or your flow should be ready to run from the list.

What You Can Do

Think in outcomes first, not in technical terms.

Ladybird is easier to learn when you start with the result you want to see on the page.

Add buttons, links, and areas to a page.

Place your own quick actions on top of sites you use often, without rebuilding the site itself.

Turn repeated clicks and typing into a reusable flow.

Save common page actions so you do not have to repeat the same sequence every time.

Hide distracting sections and common ads.

Remove banners, sidebars, repeated notices, or noisy blocks that get in your way.

Reuse passwords safely through the Password Vault.

Bind saved passwords to flow steps instead of leaving plain text in your automation setup.

Move or share your setup with import and export.

Back up your saved sites, carry them to another machine, or send a configuration to teammates.

Core Features

Each tab has a clear job inside the workflow.

Start simple. Use one tab for the immediate problem, then combine features only when you need more.

Elements

Place visible helpers directly on the current page.

Best when you want a button, link, tooltip, or area to appear exactly where you need it.

  • Add four element types: button, link, tooltip, and area.
  • Pick a position on the page instead of guessing where it should go.
  • Connect a button to a URL, selector action, or saved flow.

Reminder: start with a stable page location so your element is easier to keep working after site updates.

Flows

Save repeated page work as a flow you can run again.

Best for clicks, typing, waiting, branching, confirmations, or multi-step actions that happen often.

  • Build steps for click, input, wait, navigate, popup, assertions, conditions, loops, variables, and data sources.
  • Record page actions to create a draft, then edit the steps later.
  • Run a flow from the list and watch status, current step, and execution logs.

Reminder: if a page changes often, flows may need selector updates before they run cleanly again.

Hidden

Remove the parts of a site you do not want to keep seeing.

Best for banners, repeated prompts, side sections, and clutter that makes a page harder to use.

  • Create manual hidden rules for the current site with the element picker.
  • Pause or enable individual rules without deleting them.
  • Use the built-in automatic ad blocking toggle separately from your own rules.

Reminder: manual hidden rules belong to a site, while automatic ad blocking is a separate global switch.

Overview

See what you have already saved for each site.

Best when you want a quick inventory before cleanup, export, or troubleshooting.

  • Review how many elements, flows, and hidden rules exist per site.
  • Spot which sites have the most saved customization.
  • Delete all saved data for one site when you want a clean reset.

Reminder: Overview is the fastest place to understand your saved footprint before importing or deleting anything.

Password Vault

Keep saved passwords out of plain-text flow steps.

Best for login or secure input steps where you want reuse without exposing the value inside the flow.

  • Create a local vault password, then add named password entries.
  • Bind a saved password to a flow step instead of typing the value directly.
  • Unlock the vault during a run and continue from the current step, even from the page prompt.

Reminder: if you forget the vault password, the stored vault data cannot be recovered and must be reset.

Settings

Control language, backups, sharing, and data transfer.

Best when you are moving devices, sharing a setup, or adjusting the side panel language.

  • Import and export saved configuration as JSON.
  • Optionally include Password Vault data during export and import.
  • Switch the side panel language and open or copy the store link.

Reminder: exported files are your responsibility to store safely, especially if they include vault data.

Typical Scenarios

These are the kinds of problems Ladybird is good at solving.

Each example below follows the same pattern: what hurts now, how Ladybird helps, and what you get back.

Add quick-report buttons to an internal dashboard.

Problem

You keep opening the same report pages through several clicks inside a busy back-office tool.

Ladybird

Create page buttons or links in Elements so the shortcuts live exactly where you work.

Result

Your most-used destinations become one click away on the page you already have open.

Turn repeated form entry into a runnable flow.

Problem

You enter the same fields again and again across a form or a sequence of screens.

Ladybird

Build a flow with click, input, wait, and optional data-source steps so the sequence is reusable.

Result

The routine turns into a saved process that is faster to repeat and easier to standardize.

Bind login steps to the Password Vault instead of typing passwords into flows.

Problem

You want login automation, but keeping a password directly inside the flow is a bad habit.

Ladybird

Save the password once in the Password Vault, then bind that entry to the input step.

Result

You keep the convenience of reuse without leaving the secret as plain text in your flow setup.

Remove banners, side panels, and repeated notices from a noisy page.

Problem

The page is technically usable, but banners and repeated blocks make the work area harder to read.

Ladybird

Create a hidden rule for the distracting area and keep automatic ad blocking separate for global use.

Result

You get a calmer page layout that keeps the useful content visible and the noise out of the way.

Safety & Limits

What stays local, and what can still go wrong.

Ladybird aims to be practical and transparent. The key limits come from websites changing under you, not from hidden cloud processing.

Your saved setup stays local by default.

Elements, flows, hidden rules, and related settings are stored locally in the browser unless you export them yourself.

Password Vault data is stored as local encrypted data.

The vault is designed so passwords are not handled like normal plain-text flow values.

Exported files need your own care.

If you export configuration, especially with vault data included, you are responsible for keeping that file secure.

Some sites can be unstable targets.

Pages with frequent DOM changes, strict CSP policies, or cross-origin iframes may reduce placement or automation reliability.

Flow success still depends on the page state.

If the page changes, loads slowly, or the selector is no longer correct, the run may pause, fail, or need updates.

FAQ

Common questions from first-time users.

Should I start with Elements or Flows?

Start with Elements when you want to place something visible on the page. Start with Flows when the real goal is to automate several actions in sequence.

Why does a flow sometimes fail to run?

Usually because the page changed, loaded differently, or a saved selector no longer matches the current screen. Running depends on the page being in the expected state.

Why can’t I save a password directly as plain text in a password input flow step?

Ladybird is designed to push password use toward the Password Vault instead, so secrets are handled separately from normal flow text.

Why did my rule stop working after the site changed?

Website updates can change structure, labels, or placement. When that happens, the saved target may need to be picked again or edited.

How do I move my setup to another computer?

Use Settings to export your data as JSON, then import that file on the other machine. If you also need passwords, include the vault data during export and import it with the correct vault password.

What happens if I forget the Password Vault password?

The vault cannot be recovered without that password. You will need to reset the vault and then bind the affected flow steps again.

More Resources

Advanced links, references, and testing pages.