Reusable field transfer for repetitive web workflows
FieldTransfer is designed for situations where the same information has to be copied repeatedly from one web page and entered into another. Instead of hard-coding a particular website, the user teaches the extension which source elements to read and which target elements should receive each value.
Do you keep copying the same information from one website and pasting it into another?
Many business and clinical web systems still do not exchange data directly. When there is no API, export function or formal integration, the user becomes the integration layer — reading a value from one page, switching tabs, finding the matching field and typing or pasting it again.
Would you rather teach the browser that workflow once and reuse it?
FieldTransfer lets you define where information comes from and where it should go, then reuse that mapping whenever the same task returns. It is designed for the awkward space between fully manual data entry and expensive custom system integration.
Source elements it can learn
- Standard text and form inputs
- Textareas
- Select/drop-down fields
- Checkboxes and radio-button values
- Contenteditable elements
- Table cells and table headers
- Normal page text and useful text-containing elements
- Currently selected text can be turned into a source field
Target-field handling
- Input and textarea values
- Select fields with value/text matching
- Checkbox state conversion from common true/false-style values
- Radio groups matched by value or visible label
- Contenteditable targets
- Native value setters are used for framework-controlled inputs
input,change,keyupandblurevents are fired after writing
element.value. FieldTransfer uses the native setter where possible and emits normal form events so the target application has a better chance of recognizing the change.Profiles
- Create named source → target transfer relationships
- Each profile remembers learned source and target selectors
- Source samples are retained locally to make target mapping easier
- Target learning uses a drop-down of previously learned source fields
- The target-field chooser appears next to the field being taught
- Free version supports up to 2 saved profiles
- Profiles can be deleted from the extension popup
- Free version does not include profile import/export
Selector strategy
When an element is taught, FieldTransfer first tries stable unique identifiers such as an element ID or name. It can also use attributes such as data-testid, data-field, aria-label, title and placeholder. When no stable unique attribute is available, it builds a structural CSS selector from the page hierarchy.
Languages
The interface can follow Chrome automatically or be selected manually.
Local-first privacy model
- Transfer profiles are stored in Chrome local storage
- Copied transfer data is stored locally in the browser while being moved between pages
- No external server synchronization in the Free version
- Profile data and selected field values are not transmitted to the developer
- No profile export/import in the Free version
Chrome permissions
| Permission | Why it is requested |
|---|---|
| storage | Stores user-created profiles, the transfer buffer and interface language preference locally. |
| scripting | Starts source/target teaching and copy/paste logic on the active page after user interaction. |
| activeTab | Allows the extension to act on the page the user has actively selected. |
| clipboardWrite | Declared by the current extension manifest for transfer-related clipboard capability. |
| <all_urls> | FieldTransfer may be taught on different websites, so its host permission cannot be limited to one fixed domain. |
<all_urls> permission is present.