<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel><title>EchoFill Blog</title><link>https://echofill.app/blog/</link><description>Guides to filling forms faster in Chrome.</description><language>en-us</language>
  <atom:link href="https://echofill.app/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <item><title>Government form timed out? How to stop losing your answers</title><link>https://echofill.app/blog/government-form-timed-out.html</link><guid isPermaLink="true">https://echofill.app/blog/government-form-timed-out.html</guid><pubDate>Fri, 06 Nov 2026 08:00:00 -0800</pubDate><description>A government form timed out and you lost your data? Why long forms expire, which fixes really keep your answers, and how to refill a form in one click.</description><enclosure url="https://echofill.app/blog/images/government-form-timed-out/thumb.jpg" type="image/jpeg" length="0"/><content:encoded><![CDATA[<p><img src="https://echofill.app/blog/images/government-form-timed-out/thumb.jpg" alt=""></p>        <p>You're halfway through a long government form. It asks for a document number you don't know by heart, so you go and find it. When you come back and click Next, the page says your session has expired. Everything on that page is gone, and some sites send you back to step one.</p>
        <p><strong>The short answer:</strong> a government form times out because the site ends your session after a stretch with no activity, and on many sites typing doesn't count, only page loads do. Anything on the unsaved page is lost. The site's own Save or Next button protects the pages you've finished. Recording your answers in a form filler protects the page you're on, so a timeout costs a click instead of a retype.</p>
        <p>It happens on visa applications, tax and benefits portals, DMV renewals and permit forms, and it always seems to hit on the longest page. Below: why these forms time out, which of the usual fixes keep your data, what's safe to save, and how to set things up so a timeout doesn't cost you twenty minutes.</p>
        <h2 id="why-do-government-forms-time-out-so-fast">Why do government forms time out so fast?</h2>
        <p>Most government sites end your session after a short period of inactivity, for security. A form full of your address, date of birth and passport number shouldn't sit open on a library computer all afternoon. The catch is that "inactivity" often means "no page loads", not "no typing". You can type for 25 minutes on one long page, and to the server you've been idle the whole time.</p>
        <p>The US visa application (DS-160) is a well-known example. The official site says it "will time out after 20 minutes of inactivity, and you will lose all unsaved information" (<a href="https://ceac.state.gov/GENNIV/" rel="noopener" target="_blank">CEAC</a>). The same page tells you to save your application often and to write down the Application ID shown at the top right, because you need it to get back in if you close the browser.</p>
        <p>Sites also crash or slow to a crawl near deadlines. The defense is the same: save often, so less of your work lives only in the open page.</p>
        <h2 id="what-each-fix-actually-protects">What each fix actually protects</h2>
        <p>There are four common ways to protect a long form. They protect different things, and none of them covers everything.</p>
        <div class="table-wrap"><table class="post-table"><thead><tr><th scope="col">What you do</th><th scope="col">What survives a timeout</th><th scope="col">What it doesn't cover</th></tr></thead><tbody><tr><td data-label="What you do">Click the site's <strong>Save</strong> or <strong>Next</strong> often</td><td data-label="What survives a timeout">Every page you saved, on the agency's server</td><td data-label="What it doesn&#x27;t cover">The page you were typing on when it expired</td></tr><tr><td data-label="What you do">Draft long answers in a notes app first</td><td data-label="What survives a timeout">Whatever you wrote in the note</td><td data-label="What it doesn&#x27;t cover">Dropdowns, dates and checkboxes. You still re-enter each one</td></tr><tr><td data-label="What you do">Rely on Chrome's built-in autofill</td><td data-label="What survives a timeout">Name, address, phone, email</td><td data-label="What it doesn&#x27;t cover">Case numbers, household details, custom dropdowns, most other fields</td></tr><tr><td data-label="What you do">Record the form with EchoFill</td><td data-label="What survives a timeout">Every recorded answer, in your own browser</td><td data-label="What it doesn&#x27;t cover">A new answer you haven't recorded yet, passwords and SSNs</td></tr></tbody></table></div>
        <p>Use the site's own save button no matter what else you do. It's the only option that keeps your progress on the agency's side, so you can finish another day or on another computer.</p>
        <figure><img src="https://echofill.app/blog/images/government-form-timed-out/where-answers-survive.png" alt="Diagram comparing where your answers survive a session timeout: only typed on the page, saved with the site&#x27;s Save button, or recorded in EchoFill" width="1200" height="600" loading="lazy" decoding="async"><figcaption>Where your answers live decides whether a timeout costs you a click or a page</figcaption></figure>
        <h2 id="what-we-d-never-save-in-any-autofill-tool">What we'd never save in any autofill tool</h2>
        <p>Some answers are fine to reuse. Others aren't. EchoFill never records passwords, card numbers or Social Security numbers, even if they're on the page when you click Record. Other ID numbers, like a passport or driver's license number, are ordinary text fields to EchoFill, so whether you keep them is your call.</p>
        <p>A simple way to decide:</p>
        <ul><li><strong>Fine to save:</strong> name, address, phone, email, date of birth, employer, school, household members' names, and the "how did you hear about us" kind of answer.</li><li><strong>Think first:</strong> passport, driver's license and case numbers. They're handy to refill, and they're also exactly what an identity thief wants. If you'd rather not keep one, open Settings, pick the profile and click the ✕ next to that answer.</li><li><strong>Never reuse without reading:</strong> answers that change, like income, travel dates, your current employer, and the declarations at the end ("I certify that…"). Answer those fresh every time.</li></ul>
        <p>Your profiles stay in your browser's storage on your computer. There's no account and nothing is sent to us. Pro's optional sync uses your browser's own sync and is off unless you turn it on. That protects you from a company breach, but not from someone using your unlocked laptop. On a shared or public computer, don't record official forms at all.</p>
        <h2 id="how-to-stop-losing-data-when-a-government-form-times-out">How to stop losing data when a government form times out</h2>
        <p>The idea: get your answers out of the page and into your browser before the session has a chance to expire.</p>
        <ol><li><strong>Fill the first page normally.</strong> Use your real documents and take your time.</li><li><strong>Click the EchoFill button, then Record this form,</strong> before you click Next. Name the profile after the form, like "DMV renewal" or "Household details". You can record a half-finished page; EchoFill saves whatever is filled in.</li><li><strong>Tick Fill automatically next time</strong> and allow the site when your browser asks.</li><li><strong>Keep going.</strong> On a site you've approved, EchoFill also saves new answers you type on later pages as you go, and a small notice tells you how many it saved.</li><li><strong>If the session expires, sign back in and open the form again.</strong> EchoFill fills what it knows as soon as the page loads. It only fills empty boxes, so nothing you've already typed gets replaced.</li><li><strong>Check what filled.</strong> If anything looks wrong, click <strong>Undo</strong> and the page goes back to how it was.</li></ol>
        <div class="cta-inline"><b>Stop retyping the same answers.</b><a class="btn btn-primary" href="https://chromewebstore.google.com/detail/echofill/hejhcpofobcnifcgodjifdpipdfjdpmh">Add to Chrome, it's free</a></div>
        <p>Two settings help on slow government sites. If the form loads its boxes a second or two after the page appears, set <strong>Wait before filling</strong> to 1 or 2 seconds under the profile's <strong>Profile settings</strong>. And because EchoFill never changes an answer it has already saved, update a changed answer yourself: click <strong>Record this form</strong> and choose <strong>Update an existing profile</strong>, or edit the answer in Settings.</p>
        <p>There's more on this setup on our <a href="https://echofill.app/use-cases/government-forms.html">government and civic forms page</a>.</p>
        <h2 id="habits-that-save-you-on-any-long-form">Habits that save you on any long form</h2>
        <p>These work with or without a form filler:</p>
        <ul><li><strong>Find your documents first.</strong> Most timeouts happen while you're hunting for a number. Put your passport, license, last year's tax return and any case numbers on the desk before you start.</li><li><strong>Save on every page.</strong> If there's a Save button, use it each time. If there's an application ID, write it down the moment it appears.</li><li><strong>Don't leave a page sitting.</strong> Need a break? Click Next or Save first.</li><li><strong>Stick to one tab.</strong> Opening the same application in two tabs can confuse some sites and end both sessions.</li><li><strong>Read the last page fresh.</strong> The certification and signature steps are yours to answer. EchoFill fills fields but never submits anything; you press Submit yourself.</li></ul>
        <p>If you only take one thing from this: put your documents on the desk before you open the form. A deadline form is the worst place to find out how short the timeout is.</p>
        <h2 id="frequently-asked-questions">Frequently asked questions</h2>
        <details><summary>Can I recover a government form after the session timed out?</summary>
        <p>Usually not from the page itself. Once the server ends your session, the answers on the unsaved page are gone, and pressing Back rarely brings them back. What you can get back is anything you saved with the site's Save button or recorded in a form filler beforehand.</p>
        </details>
        <details><summary>Why does the DS-160 keep timing out?</summary>
        <p>The official site times you out after 20 minutes of inactivity. Time spent typing on one page may not count as activity, so click Next or Save often, write down your Application ID, and gather your passport and travel details before you start.</p>
        </details>
        <details><summary>Is it safe to autofill government forms?</summary>
        <p>For stable details like your name and address, yes, if the tool keeps your data on your device and you check every field. Read income, travel dates and the final declarations yourself every time. EchoFill fills fields but never submits a form for you.</p>
        </details>
        <details><summary>Will autofill mess up a government form?</summary>
        <p>It can if a saved answer is out of date, which is why you should look over every filled field before clicking Next. EchoFill outlines what it filled, and Undo puts the page back the way it was in one click.</p>
        </details>
        <div class="news "><div class="news-copy"><b>Get new form-filling guides by email</b><p>One short email when we publish a new guide. No spam, unsubscribe anytime.</p></div><form class="news-form" action="https://buttondown.com/api/emails/embed-subscribe/echofill" method="post" target="_blank" data-news><label class="sr" for="nl-email-31">Email address</label><input id="nl-email-31" type="email" name="email" required placeholder="you@example.com" autocomplete="email"><input type="hidden" name="embed" value="1"><button class="btn btn-primary" type="submit">Subscribe</button><p class="news-ok" role="status" hidden>Almost done: check your inbox and click the confirmation link.</p><p class="news-fine">By subscribing you agree to our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p></form></div>]]></content:encoded></item>
    <item><title>Chrome autofill putting the wrong info in fields? How to fix it</title><link>https://echofill.app/blog/chrome-autofill-wrong-info.html</link><guid isPermaLink="true">https://echofill.app/blog/chrome-autofill-wrong-info.html</guid><pubDate>Wed, 04 Nov 2026 08:00:00 -0800</pubDate><description>Chrome autofill filling in wrong information? An old address, your full name in every name box, a street in the notes. Why it happens and how to fix each one.</description><enclosure url="https://echofill.app/blog/images/chrome-autofill-wrong-info/thumb.jpg" type="image/jpeg" length="0"/><content:encoded><![CDATA[<p><img src="https://echofill.app/blog/images/chrome-autofill-wrong-info/thumb.jpg" alt=""></p>        <p>You click into a form, Chrome offers your details, and you accept. It looks done. Then you notice the middle name box says your full name, the shipping address is the apartment you left last year, and "Delivery instructions" now holds your street. If you don't catch it, that's what the company gets.</p>
        <p><strong>The short answer:</strong> when Chrome autofill puts wrong information in a field, it's almost always one of two things. Either the saved entry is out of date, or the form's labels make Chrome guess wrong about what a box is for. You fix the first in Chrome's settings under Passwords and autofill. The second is the form's fault, so you check those boxes by hand before you submit.</p>
        <p>Below: why Chrome guesses wrong, how to fix a bad saved entry, what to do when the info is right but lands in the wrong box, and how to make forms you fill often come out the same way every time.</p>
        <h2 id="why-does-chrome-autofill-put-the-wrong-information-in-a-fiel">Why does Chrome autofill put the wrong information in a field?</h2>
        <p>Chrome doesn't know what a field is for. It guesses. When a page loads, Chrome reads each field's name, its label and its <code>autocomplete</code> attribute, and matches them against patterns for things it knows: name, email, phone, street, city, ZIP. If a pattern matches, the field gets that piece of your saved address.</p>
        <p>Usually the guess is right. When it isn't, it tends to be one of these:</p>
        <ul><li><strong>A label contains a trigger word.</strong> One developer found orders arriving with the first line of the address copied into "Delivery instructions". The label included the word "address", which matched Chrome's pattern for street line 1. Rewording the label without that word fixed it (<a href="https://michaelbromley.co.uk/blog/fixing-chrome-autofill-mysterious-wrong-values-solved" rel="noopener" target="_blank">Michael Bromley</a>).</li><li><strong>Name boxes with no label of their own.</strong> A name split into First, Middle and Last, with no "First" or "Last" under each box, can get your full name in every one. In one <a href="https://www.jotform.com/answers/2906285-name-duplicates-full-name-is-entered-in-both-the-first-and-last-name-field" rel="noopener" target="_blank">Jotform support thread</a>, the form owner had removed those sublabels, and putting them back fixed it. A <a href="https://www.machform.com/forums/topic/browser-autofill-putting-full-name-into-middle-name-or-other-name-fields" rel="noopener" target="_blank">MachForm forum post</a> describes the same thing ending up as "John Smith John Smith John Smith".</li><li><strong>The saved entry is old.</strong> You moved, changed numbers or switched email, and Chrome still has the old version. Or it has two versions and offers the wrong one first.</li></ul>
        <p>Only the last one is something your settings can fix. The other two come from the form, and Chrome will make the same guess on that page every time you visit.</p>
        <figure><img src="https://echofill.app/blog/images/chrome-autofill-wrong-info/three-mistakes.png" alt="A sample form with three common Chrome autofill mistakes: a full name repeated in three name boxes, a street address placed in a Delivery instructions box, and an old saved address, each with its cause and fix" width="1200" height="560" loading="lazy" decoding="async"><figcaption>Three ways Chrome autofill gets a form wrong, and what causes each</figcaption></figure>
        <h2 id="how-to-fix-a-wrong-or-old-saved-address-in-chrome">How to fix a wrong or old saved address in Chrome</h2>
        <p>If Chrome keeps offering an old address, phone or email, edit or delete the saved entry. On a computer (<a href="https://support.google.com/chrome/answer/142893?hl=en" rel="noopener" target="_blank">Google's steps</a>):</p>
        <ol><li>Click the three dots at the top right of Chrome, then <strong>Passwords and autofill</strong>.</li><li>Open the section that holds your addresses. Depending on your Chrome version it may be called addresses or contact info.</li><li>Next to the wrong entry, click the three dots and choose <strong>Edit</strong> to correct it or <strong>Delete</strong> to remove it.</li></ol>
        <p>That covers saved addresses. The other kind of suggestion, something you once typed into a box that Chrome now offers back, is form history. To remove one entry, start typing so the suggestion shows up, highlight it with the arrow keys and press <strong>Shift + Delete</strong> (on a Mac, <strong>Shift + Fn + Delete</strong>). To clear all of it, open the three dots, choose <strong>Delete browsing data</strong>, pick a time range, and tick <strong>Autofill form data</strong> under Advanced. That removes everything, not just the one bad entry.</p>
        <p>If you'd rather Chrome stopped filling addresses altogether, switch off <strong>Save and fill addresses</strong> in the same settings section.</p>
        <h2 id="when-the-info-is-right-but-lands-in-the-wrong-field">When the info is right but lands in the wrong field</h2>
        <p>If your saved address is correct and Chrome still drops it in the wrong boxes, no setting will help. Chrome reads that page the same way every time. Here's what you can do instead:</p>
        <div class="table-wrap"><table class="post-table"><thead><tr><th scope="col">What you see</th><th scope="col">Likely cause</th><th scope="col">What to do</th></tr></thead><tbody><tr><td data-label="What you see">Old address or phone offered first</td><td data-label="Likely cause">Stale saved entry</td><td data-label="What to do">Edit or delete it in Passwords and autofill</td></tr><tr><td data-label="What you see">Full name in First, Middle and Last</td><td data-label="Likely cause">The name boxes have no labels of their own</td><td data-label="What to do">Fix by hand; tell the site if it's yours</td></tr><tr><td data-label="What you see">Street address in a notes or instructions box</td><td data-label="Likely cause">The label contains "address" or a similar word</td><td data-label="What to do">Clear the box before you submit</td></tr><tr><td data-label="What you see">A random old value in a custom box</td><td data-label="Likely cause">Form history, not a saved address</td><td data-label="What to do">Shift + Delete on that suggestion</td></tr><tr><td data-label="What you see">Two tools fill the same box differently</td><td data-label="Likely cause">Chrome and an extension both filling</td><td data-label="What to do">Turn one off for that kind of data</td></tr></tbody></table></div>
        <p>If you run the site, the fix is on your end: give every box its own label and set the right <code>autocomplete</code> value (<code>given-name</code>, <code>family-name</code>, <code>address-line1</code>). Chrome's DevTools has an Autofill panel that shows what Chrome thinks each field is. We walked through it in <a href="https://echofill.app/blog/chrome-autofill-not-filling-fields.html">why Chrome autofill skips fields</a>.</p>
        <p>On our own computers we turned Chrome's address autofill off. EchoFill was already filling those fields, we didn't need both, and the two sometimes fought over the same box.</p>
        <h2 id="how-to-make-a-form-fill-the-same-way-every-time">How to make a form fill the same way every time</h2>
        <p>A guess can be wrong. A recording of what you typed into one specific form isn't a guess. That's the idea behind EchoFill, a free extension for Chrome, Edge and Firefox that remembers a form and puts your answers back in the same boxes next time. Everything stays in your browser.</p>
        <ol><li><strong>Fill the form once by hand, correctly.</strong> Pay attention to the fields Chrome usually gets wrong.</li><li><strong>Click the EchoFill button, then Record this form.</strong> Name the profile something you'll recognize, like "Home address (new)". EchoFill never saves passwords, card numbers or Social Security numbers.</li><li><strong>Next time, click Autofill.</strong> EchoFill matches each field by its label, name and placeholder, the way you filled it. If you left the middle name empty, it stays empty.</li><li><strong>Check it.</strong> If anything filled wrong, <strong>Undo</strong> puts every field back in one click. When your details change, correct the field, click <strong>Record this form</strong> and choose <strong>Update an existing profile</strong>. From then on the profile has the new version.</li></ol>
        <p>You can keep separate profiles for separate versions of you: home and work address, or one per person if you share a computer. The free plan includes 3 profiles.</p>
        <div class="cta-inline"><b>Stop retyping the same answers.</b><a class="btn btn-primary" href="https://chromewebstore.google.com/detail/echofill/hejhcpofobcnifcgodjifdpipdfjdpmh">Add to Chrome, it's free</a></div>
        <p>One catch if Chrome's autofill is still on: EchoFill fills only empty fields by default, so a box Chrome already filled wrong stays wrong. To let your recorded answer win, open the profile in Settings, expand <strong>Profile settings</strong> and turn on <strong>Overwrite fields that already have an answer</strong>.</p>
        <p>EchoFill isn't perfect either. On a site you haven't recorded, it also matches by label, so a strangely labeled box can still get the wrong value. That's what Undo is for. It doesn't fill rich-text editors yet.</p>
        <h2 id="a-20-second-check-before-you-hit-submit">A 20-second check before you hit Submit</h2>
        <p>Whatever fills your forms, this catches almost every wrong autofill:</p>
        <ul><li>Name: first, middle and last each hold one name, or nothing</li><li>Address: it's your current one, and the unit or apartment number is right</li><li>Phone and email: the ones you actually check now, not an old work address</li><li>Notes, instructions and "anything else" boxes: empty unless you typed in them</li><li>Anything legal or one-off, like dates, signatures and attestations: read it yourself</li></ul>
        <p>Manufacturing has a name for this habit: poka-yoke, or mistake-proofing. Set things up so the same error can't slip through twice. A recorded form plus a quick look before Submit gets you most of the way there.</p>
        <h2 id="frequently-asked-questions">Frequently asked questions</h2>
        <details><summary>Why does Chrome autofill the wrong address?</summary>
        <p>Usually an old address is still saved in Chrome, or there are two and the old one comes first. Go to the three dots, Passwords and autofill, open the addresses section, and edit or delete the wrong entry. If the right address lands in the wrong boxes instead, the form's labels are confusing Chrome, and changing settings won't fix that.</p>
        </details>
        <details><summary>How do I delete one wrong autofill suggestion in Chrome?</summary>
        <p>Start typing in the box so the suggestion appears, highlight it with the arrow keys, then press Shift + Delete (Shift + Fn + Delete on a Mac). Saved addresses are removed from the settings page instead. Clearing "Autofill form data" deletes all form history at once.</p>
        </details>
        <details><summary>Why does Chrome put my full name in the first name field?</summary>
        <p>Chrome decides what a box is for from its label and name. When a form splits your name into several boxes without labeling each one, Chrome can put the full name in all of them. Fix the boxes by hand before you submit. If the form is yours, label each box and set <code>autocomplete</code> to <code>given-name</code> and <code>family-name</code>.</p>
        </details>
        <details><summary>Will EchoFill and Chrome both fill the same field?</summary>
        <p>They can both try. EchoFill fills only empty fields by default, so it won't overwrite what Chrome already put there, right or wrong. Turn on "Overwrite fields that already have an answer" in a profile's settings if you want EchoFill's answer to win. If the two keep disagreeing on a form you use often, turn off Chrome's address filling and let the recorded version handle it.</p>
        </details>
        <div class="news "><div class="news-copy"><b>Get new form-filling guides by email</b><p>One short email when we publish a new guide. No spam, unsubscribe anytime.</p></div><form class="news-form" action="https://buttondown.com/api/emails/embed-subscribe/echofill" method="post" target="_blank" data-news><label class="sr" for="nl-email-33">Email address</label><input id="nl-email-33" type="email" name="email" required placeholder="you@example.com" autocomplete="email"><input type="hidden" name="embed" value="1"><button class="btn btn-primary" type="submit">Subscribe</button><p class="news-ok" role="status" hidden>Almost done: check your inbox and click the confirmation link.</p><p class="news-fine">By subscribing you agree to our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p></form></div>]]></content:encoded></item>
    <item><title>Why job applications make you retype your resume (and how to stop)</title><link>https://echofill.app/blog/retype-resume-job-applications.html</link><guid isPermaLink="true">https://echofill.app/blog/retype-resume-job-applications.html</guid><pubDate>Mon, 02 Nov 2026 08:00:00 -0800</pubDate><description>You upload your resume, then re-enter it all by hand. Why applicant tracking systems ask twice, what the parser gets wrong, and how to stop retyping it.</description><enclosure url="https://echofill.app/blog/images/retype-resume-job-applications/thumb.jpg" type="image/jpeg" length="0"/><content:encoded><![CDATA[<p><img src="https://echofill.app/blog/images/retype-resume-job-applications/thumb.jpg" alt=""></p>        <p>You upload your resume. The page thinks for a second, then shows you a form with your name split wrong, a job title sitting in the company box, and three of your five jobs missing. So you fix it field by field and type out the rest. Tomorrow you do it again on another company's site.</p>
        <p><strong>The short answer:</strong> job applications make you re-enter your resume because each employer's applicant tracking system stores your history as separate, searchable fields, and the "upload your resume" step only guesses at what goes where. Nothing carries over from one company to the next. You can't change that, but you can get a cleaner parse and stop typing the same answers twice.</p>
        <p>We've been there. On our own job searches, many of them on Workday, retyping a name, contact details, an address and a description for every past role took more than half the time on a lot of applications.</p>
        <p>Below: why the form asks twice, what trips up the parser, and three ways to stop retyping, one of which uses no AI and uploads nothing.</p>
        <h2 id="why-do-job-applications-make-you-re-enter-your-resume">Why do job applications make you re-enter your resume?</h2>
        <p>A resume is a document for people. An application is a database for software. Most employers run an applicant tracking system (ATS) such as Workday, Greenhouse, Lever, iCIMS or Taleo, and recruiters filter it by fields: job title, employer, dates, degree, location. You can't filter a PDF. You can filter fields.</p>
        <p>A few other reasons, none of them about you:</p>
        <ul><li><strong>Every employer has its own copy.</strong> Your profile on one company's Workday site doesn't follow you to the next company, even when the pages look the same.</li><li><strong>Parsing is a guess.</strong> The upload step reads your file and guesses which text belongs in which box. When it guesses wrong, you're asked to fix it.</li><li><strong>Some questions aren't on any resume.</strong> Work authorization, sponsorship, "How did you hear about us?", your start date and the voluntary self-identification questions have to be asked directly.</li></ul>
        <p><a href="https://www.jobscan.co/blog/re-entering-info-after-uploading-resume/" rel="noopener" target="_blank">Jobscan</a> points out that recruiters often search for skills and keywords to narrow the pool before they look at a single resume, and the typed fields help those searches. So "see resume" in a text box is a bad idea, however tempting it is at 11pm.</p>
        <h2 id="what-does-the-resume-parser-get-wrong">What does the resume parser get wrong?</h2>
        <p>Mostly anything that isn't plain, single-column text in the usual order. Greenhouse's help center lists the common causes in its article on an <a href="https://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parse" rel="noopener" target="_blank">unsuccessful resume parse</a>:</p>
        <div class="table-wrap"><table class="post-table"><thead><tr><th scope="col">What's in your resume</th><th scope="col">What tends to happen</th></tr></thead><tbody><tr><td data-label="What&#x27;s in your resume">Name and contact details in the header, footer or a text box</td><td data-label="What tends to happen">Name, email or phone come through empty</td></tr><tr><td data-label="What&#x27;s in your resume">Columns, tables or text boxes</td><td data-label="What tends to happen">Text is read out of order or skipped</td></tr><tr><td data-label="What&#x27;s in your resume">Saved as an image, or a scanned PDF</td><td data-label="What tends to happen">Nothing parses</td></tr><tr><td data-label="What&#x27;s in your resume">A file larger than 2.5 MB</td><td data-label="What tends to happen">The parser can't read it at all</td></tr><tr><td data-label="What&#x27;s in your resume">Shortened titles like "Sr. Account Exec"</td><td data-label="What tends to happen">The title is misread or dropped</td></tr><tr><td data-label="What&#x27;s in your resume">Letters spaced out for style</td><td data-label="What tends to happen">Not read as words</td></tr><tr><td data-label="What&#x27;s in your resume">Employer names without Inc., Co. or LLC</td><td data-label="What tends to happen">The company may be missed</td></tr></tbody></table></div>
        <p>The partial parse is the sneaky one. Some boxes fill and some don't, and the ones that did fill can still be wrong. Greenhouse's own advice for a partial parse is that the fields need to be "manually corrected and verified."</p>
        <figure><img src="https://echofill.app/blog/images/retype-resume-job-applications/parse-vs-recorded.png" alt="A fictional application filled two ways: after a resume parse, first name, email and start date are empty and the job title and employer are swapped; with recorded answers, all five fields hold the right values" width="1200" height="560" loading="lazy" decoding="async"><figcaption>What a parser guesses vs. what you recorded yourself</figcaption></figure>
        <h2 id="three-ways-to-stop-retyping-your-resume">Three ways to stop retyping your resume</h2>
        <p>You can't change how an employer sets up its system. You can change how much typing each application costs you.</p>
        <h3 id="1-make-your-resume-easier-to-parse">1. Make your resume easier to parse</h3>
        <p>One column. Standard headings such as "Experience", "Education" and "Skills". Contact details in the body, not the header. Full job titles. A .docx or a text-based PDF well under 2.5 MB. It won't make every parse perfect, but there's less to fix afterwards.</p>
        <h3 id="2-keep-one-source-of-truth-file">2. Keep one "source of truth" file</h3>
        <p>A plain text file with each employer's exact name, your exact titles, start and end months, your degree and school, and a short description of each role. When a form asks, copy from it instead of rewording from memory. Your dates and titles then match on every application, which matters if a background check compares them later.</p>
        <h3 id="3-let-your-browser-fill-in-your-own-answers">3. Let your browser fill in your own answers</h3>
        <p>Fill one application carefully, once, and have those answers filled back in on the next one. That's the job we built EchoFill for. It doesn't read your resume. It records what you typed into the form and fills fields with matching labels on the next application, in your browser, with nothing uploaded and no AI involved.</p>
        <h2 id="how-to-autofill-job-applications-from-your-own-answers">How to autofill job applications from your own answers</h2>
        <ol><li><strong>Fill one application by hand.</strong> Pick a posting you were going to apply to anyway and fill in every field you can, carefully. These become your saved answers.</li><li><strong>Record each page.</strong> Before you click Next, click the EchoFill button, then <strong>Record this form</strong>. Give the profile a clear name like "Job applications".</li><li><strong>On the next application, click Autofill.</strong> EchoFill matches fields by their label, name and placeholder, so "First name" finds your first name whatever the site calls that box in its code. It also handles the custom dropdowns and type-to-search boxes that job sites use.</li><li><strong>Add what's missing.</strong> If a field stays empty, type it once, click <strong>Record this form</strong> and choose <strong>Update an existing profile</strong>. If something lands in the wrong box, <strong>Undo</strong> puts the page back the way it was.</li><li><strong>Attach your resume and read the rest.</strong> On the free plan you upload the file yourself. EchoFill Pro can keep a copy of your resume on your computer and attach it to the upload box for you. Either way, if the site parses the file when it's attached, check what it changed.</li></ol>
        <p>We haven't tried every portal, and portals change their pages, so treat your first application on a new site as a test run. On our own Workday applications, pages with fields we'd filled before filled as soon as they opened, and work history and role descriptions saved the most time. Answers tailored to one specific role we still write by hand.</p>
        <p>On a site you haven't recorded, click Autofill anyway. EchoFill fills the fields whose labels match what you saved. Pro's Universal fields go a step further and fill your name, email, phone, address and links by what each box asks for, even when the labels are worded differently. There's more on this on our <a href="https://echofill.app/use-cases/job-applications.html">job applications page</a>.</p>
        <div class="cta-inline"><b>Stop retyping the same answers.</b><a class="btn btn-primary" href="https://chromewebstore.google.com/detail/echofill/hejhcpofobcnifcgodjifdpipdfjdpmh">Add to Chrome, it's free</a></div>
        <h2 id="what-not-to-copy-from-one-application-to-the-next">What not to copy from one application to the next</h2>
        <p>Autofill is for answers that don't change. Some do, and they need fresh eyes every time:</p>
        <ul><li><strong>Eligibility questions.</strong> Work authorization and sponsorship usually have the same answer, but companies word them differently, sometimes in the negative. Read each one.</li><li><strong>Self-identification.</strong> Gender, race and ethnicity, veteran and disability questions are optional. Decide each time.</li><li><strong>Anything about this role.</strong> Salary expectations, start date, "Why do you want to work here?" and cover letters.</li><li><strong>Details that changed.</strong> A new phone number, a new address, a job you've since left. Update the profile the day it changes. An old phone number is easy to miss and expensive if a recruiter can't reach you.</li></ul>
        <p>EchoFill never records passwords, card numbers or Social Security numbers, so those stay out of your saved answers no matter what.</p>
        <h2 id="frequently-asked-questions">Frequently asked questions</h2>
        <details><summary>Why do I have to re-enter my resume if I already uploaded it?</summary>
        <p>The employer's applicant tracking system stores your history as separate fields so recruiters can search and filter it. The upload step tries to fill those fields by reading your file, but the read is a guess, and some questions aren't on a resume at all. So you're asked to check, correct and complete them.</p>
        </details>
        <details><summary>Does uploading a resume ever fill everything correctly?</summary>
        <p>Sometimes, with a simple single-column resume. Even then, check it. A partial parse can put a job title in the employer field or drop your dates, and the form will happily submit it that way.</p>
        </details>
        <details><summary>Is it safe to use an autofill extension on job applications?</summary>
        <p>It depends on where your data goes. Many job tools upload your resume and answers to their servers so an AI can write responses. EchoFill keeps your answers only in your browser on your own computer, with no account and no server copy. Our <a href="https://echofill.app/privacy.html">privacy policy</a> lists exactly what it stores.</p>
        </details>
        <details><summary>How long does it take to set up?</summary>
        <p>About as long as one careful application. Fill it, record each page as you go, and the next application is where it pays off. There's a small learning curve, and most people have it down after two or three applications.</p>
        </details>
        <details><summary>Do I need to pay for EchoFill?</summary>
        <p>No. The free plan has unlimited fills and three saved profiles, which covers most job searches. Pro ($2.99/month, $19.99/year or $29.99 once) adds unlimited profiles, resume attaching and Universal fields for sites you've never recorded. For a step-by-step on one portal, see <a href="https://echofill.app/blog/autofill-workday-applications.html">how to stop retyping Workday applications</a>.</p>
        </details>
        <div class="news "><div class="news-copy"><b>Get new form-filling guides by email</b><p>One short email when we publish a new guide. No spam, unsubscribe anytime.</p></div><form class="news-form" action="https://buttondown.com/api/emails/embed-subscribe/echofill" method="post" target="_blank" data-news><label class="sr" for="nl-email-35">Email address</label><input id="nl-email-35" type="email" name="email" required placeholder="you@example.com" autocomplete="email"><input type="hidden" name="embed" value="1"><button class="btn btn-primary" type="submit">Subscribe</button><p class="news-ok" role="status" hidden>Almost done: check your inbox and click the confirmation link.</p><p class="news-fine">By subscribing you agree to our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p></form></div>]]></content:encoded></item>
    <item><title>How to post the same ad on several sites without retyping it</title><link>https://echofill.app/blog/post-same-ad-multiple-sites.html</link><guid isPermaLink="true">https://echofill.app/blog/post-same-ad-multiple-sites.html</guid><pubDate>Fri, 16 Oct 2026 08:00:00 -0700</pubDate><description>I posted one fridge ad on Craigslist, Facebook Marketplace and local sites. Here&#x27;s how to stop retyping the same ad, without a paid crosslisting app.</description><enclosure url="https://echofill.app/blog/images/post-same-ad-multiple-sites/thumb.jpg" type="image/jpeg" length="0"/><content:encoded><![CDATA[<p><img src="https://echofill.app/blog/images/post-same-ad-multiple-sites/thumb.jpg" alt=""></p>        <p>You wrote a good ad on the first site. The title is right, the description says everything a buyer or customer needs, and your name, area and phone number are in. Then you open the second site and the form is empty again. Same boxes, slightly different labels, and you're copying and pasting one field at a time.</p>
        <p>When I moved out of my old apartment, I had a refrigerator to sell. I posted it on Craigslist, Facebook Marketplace and a few local newspaper sites, because each one reaches different people. Every site took a good chunk of time, and I was filling in the same things over and over: my phone number, the area I was in, how much I wanted for it. Using EchoFill cut that down a lot. It saved me at least 15 minutes per posting.</p>
        <p>This post covers whether you need a paid crosslisting app, what stays the same from site to site, how to post one ad everywhere with a form filler, and the posting rules that catch people out.</p>
        <h2 id="do-you-need-a-crosslisting-app">Do you need a crosslisting app?</h2>
        <p>If you resell dozens of items a month, probably yes. If you post a handful of ads, probably not.</p>
        <p>Crosslisting apps like Crosslist, Vendoo and List Perfectly are built for resellers. You connect your marketplace accounts, create a listing once, and the app publishes it to eBay, Poshmark, Mercari, Facebook Marketplace and others. The feature that earns the subscription is delisting: when an item sells on one site, the app takes it down everywhere else. That matters when you have 200 items live. Crosslist charges $29.99 to $44.99 a month (<a href="https://crosslist.com/docs/cross-listing/" rel="noopener" target="_blank">Crosslist</a>), and Vendoo's U.S. plans run from $14.99 to $59.99 a month (<a href="https://www.nifty.ai/post/vendoo-pricing" rel="noopener" target="_blank">Nifty, October 2026</a>).</p>
        <p>Most ads aren't that. A fridge from your old apartment, a room for rent, a couch, a tutoring service, a garage sale, a local event, a listing in a directory. You post it on three or four sites, it runs for a few weeks, and you take it down. For that, paying monthly and connecting every account to a third-party service is a lot of setup for a little typing.</p>
        <div class="table-wrap"><table class="post-table"><thead><tr><th scope="col"></th><th scope="col">Crosslisting app</th><th scope="col">Form filler (like EchoFill)</th><th scope="col">Copy and paste from a doc</th></tr></thead><tbody><tr><td data-label="">Cost</td><td data-label="Crosslisting app">About $15 to $60 a month</td><td data-label="Form filler (like EchoFill)">Free for 3 profiles; Pro from $2.99 a month</td><td data-label="Copy and paste from a doc">Free</td></tr><tr><td data-label="">Sites it works on</td><td data-label="Crosslisting app">Its supported marketplaces</td><td data-label="Form filler (like EchoFill)">Any site with a normal web form</td><td data-label="Copy and paste from a doc">Any site</td></tr><tr><td data-label="">Accounts connected to a third party</td><td data-label="Crosslisting app">Yes</td><td data-label="Form filler (like EchoFill)">No. Your answers stay in your browser</td><td data-label="Copy and paste from a doc">No</td></tr><tr><td data-label="">Photos</td><td data-label="Crosslisting app">Uploaded for you</td><td data-label="Form filler (like EchoFill)">You add them</td><td data-label="Copy and paste from a doc">You add them</td></tr><tr><td data-label="">Removes the ad everywhere when sold</td><td data-label="Crosslisting app">Yes, on supported sites</td><td data-label="Form filler (like EchoFill)">No</td><td data-label="Copy and paste from a doc">No</td></tr><tr><td data-label="">Best for</td><td data-label="Crosslisting app">Resellers with many items</td><td data-label="Form filler (like EchoFill)">A few ads on several sites, repeated over time</td><td data-label="Copy and paste from a doc">One ad, once</td></tr></tbody></table></div>
        <p>For what it's worth, when I sold my fridge I didn't even know crosslisting apps existed. And I don't want to install yet another app that takes up storage and memory just to post a few ads.</p>
        <h2 id="what-stays-the-same-from-site-to-site-and-what-changes">What stays the same from site to site, and what changes</h2>
        <p>Most of an ad is the same everywhere. Your name, email, phone number, city or ZIP, the title, the description, the price and the "how to reach me" line don't change because the site did.</p>
        <p>What changes is the form around it:</p>
        <ul><li><strong>Labels.</strong> One site says "Postcode", another "ZIP". One says "Headline", another "Title". A form filler that matches by label, name and placeholder handles most of these. Ones that rely on fixed field IDs don't.</li><li><strong>Categories.</strong> Every site has its own category tree. "Furniture &gt; Tables" on one is "Home &amp; Garden" on the next. You'll usually pick these by hand the first time on each site.</li><li><strong>Photos.</strong> Browsers don't let extensions attach files for you. You add photos yourself on every site, whichever tool you use. Crosslisting apps get around this by uploading through their own servers.</li><li><strong>Formatted description boxes.</strong> Some sites use a rich-text editor (the kind with bold and bullet buttons). EchoFill doesn't fill those yet, so paste the description there.</li></ul>
        <figure><img src="https://echofill.app/blog/images/post-same-ad-multiple-sites/same-vs-changes.png" alt="Diagram of an ad split into two groups: name, phone, email, ZIP, title, description and price are the same on every site and fill from one profile; category, photos and site-specific options change per site and are done by hand" width="1200" height="500" loading="lazy" decoding="async"><figcaption>Most of an ad is the same everywhere. Fill that part, do the rest by hand.</figcaption></figure>
        <h2 id="how-to-post-one-ad-on-several-sites-with-echofill">How to post one ad on several sites with EchoFill</h2>
        <p>The idea: write the ad carefully once, record it, and fill it everywhere else.</p>
        <ol><li><strong>Write the ad on the first site.</strong> Take your time here. This is the version you'll reuse, so fix typos and get the phone number right.</li><li><strong>Click EchoFill → Record this form</strong> before you submit. Name the profile after the ad ("Room for rent, Elm St" or "Weekend tutoring").</li><li><strong>Open the next site's "post an ad" page and click Autofill.</strong> EchoFill ranks your profiles by how well they match the page, so the ad you just recorded is usually at the top.</li><li><strong>Check what filled.</strong> Filled fields are outlined in green, and the popup tells you how many filled. Pick the category, add photos, and change anything that's specific to this site.</li><li><strong>Click Record this form → Update</strong> if you changed something you'll want next time on this site. Next time you post there, more of it fills.</li><li><strong>If something filled wrong, click Undo</strong> and the form goes back to how it was.</li></ol>
        <div class="cta-inline"><b>Stop retyping the same answers.</b><a class="btn btn-primary" href="https://chromewebstore.google.com/detail/echofill/hejhcpofobcnifcgodjifdpipdfjdpmh">Add to Chrome, it's free</a></div>
        <p>If you post a lot, two other setups work well. Keep one profile per ad, so you can repost any of them in a minute. Or keep a single "Contact details" profile with your name, phone, email and area, and type only the new title and description each time. The free plan holds three profiles. Pro removes that limit and adds Universal fields, which fill your contact details on a site you've never recorded by working out what each box is asking for.</p>
        <p>I keep one profile per ad. Each thing I'm selling gets its own profile, so I can post it again on any site without starting over.</p>
        <p>There's more on this setup on the <a href="https://echofill.app/use-cases/marketplace-listings.html">listings and postings page</a>.</p>
        <h2 id="posting-rules-that-catch-people-out">Posting rules that catch people out</h2>
        <p>Filling the form faster doesn't change each site's rules, and a few of them matter when you post the same ad in several places.</p>
        <ul><li><strong>Craigslist limits reposting.</strong> Its rule is one category in one area, once every 48 hours. Similar ads posted in several cities close together can be "ghosted": they look posted to you but never appear, and Craigslist doesn't tell you (<a href="https://smallbusiness.chron.com/can-post-craigslist-26630.html" rel="noopener" target="_blank">Chron</a>). Post where you actually are, and don't spray the same ad across cities.</li><li><strong>Nothing takes your ad down for you.</strong> Without a crosslisting app, when the room is rented or the couch is gone, you remove the ad on every site yourself. One reseller who crossposted by hand double-sold six items in two months before changing how they worked (<a href="https://closo.co/blogs/beginner-guides-how-tos/how-to-crosspost-on-facebook-without-losing-your-mind-quick-overview-included" rel="noopener" target="_blank">Closo</a>). Keep a short list of where each ad is live.</li><li><strong>Re-read before you post.</strong> Autofill puts in exactly what you saved. If the price dropped or the dates changed, update the profile first, or you'll post the old version everywhere.</li></ul>
        <h2 id="the-one-thing-i-d-tell-a-friend">The one thing I'd tell a friend</h2>
        <p>Post it on as many platforms as you can. Yes, the audiences overlap, but a lot of them don't. In my experience, far more don't than do. The person who'd buy your fridge might only ever check one site, and visibility is what really matters when you're selling. That's exactly where a tool like EchoFill comes in handy: adding one more site costs a few clicks instead of retyping the whole ad.</p>
        <p>Just keep it to different platforms, not the same ad copied across many cities on one site. That's what gets ads ghosted on Craigslist.</p>
        <h2 id="frequently-asked-questions">Frequently asked questions</h2>
        <details><summary>Can I post the same ad on Facebook Marketplace and Craigslist?</summary>
        <p>Yes, as long as each listing follows that site's rules. Craigslist limits you to one category in one area every 48 hours, so post in the area you're actually in. Remember to take the ad down on both when it's sold or filled.</p>
        </details>
        <details><summary>Can a form filler upload my photos too?</summary>
        <p>No. Browsers don't let extensions attach files, so EchoFill and similar tools fill the text and choices and you add photos yourself. Crosslisting apps upload photos because they post through their own servers after you connect your accounts.</p>
        </details>
        <details><summary>Is a crosslisting app worth it for a few ads?</summary>
        <p>Usually not. The main thing a subscription buys is automatic delisting across marketplaces, which matters when you have many items live at once. For a few ads that run a few weeks, a form filler or a saved document is cheaper and keeps your accounts unconnected.</p>
        </details>
        <details><summary>Does EchoFill work on sites I haven't recorded?</summary>
        <p>Yes, with a click. Open the form, click <strong>Autofill</strong>, and EchoFill fills fields whose labels, names or placeholders match what you saved, then shows you what it filled. Pro's Universal fields go further and fill common details like name, phone and ZIP by meaning, even when the labels are different.</p>
        </details>
        <div class="news "><div class="news-copy"><b>Get new form-filling guides by email</b><p>One short email when we publish a new guide. No spam, unsubscribe anytime.</p></div><form class="news-form" action="https://buttondown.com/api/emails/embed-subscribe/echofill" method="post" target="_blank" data-news><label class="sr" for="nl-email-37">Email address</label><input id="nl-email-37" type="email" name="email" required placeholder="you@example.com" autocomplete="email"><input type="hidden" name="embed" value="1"><button class="btn btn-primary" type="submit">Subscribe</button><p class="news-ok" role="status" hidden>Almost done: check your inbox and click the confirmation link.</p><p class="news-fine">By subscribing you agree to our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p></form></div>]]></content:encoded></item>
    <item><title>Chrome autofill not filling every field? Why, and the fix</title><link>https://echofill.app/blog/chrome-autofill-not-filling-fields.html</link><guid isPermaLink="true">https://echofill.app/blog/chrome-autofill-not-filling-fields.html</guid><pubDate>Wed, 14 Oct 2026 08:00:00 -0700</pubDate><description>Chrome fills your name and address, then leaves the rest blank. Here&#x27;s how to check your settings, why it skips fields by design, and how to fill the rest.</description><enclosure url="https://echofill.app/blog/images/chrome-autofill-not-filling-fields/thumb.jpg" type="image/jpeg" length="0"/><content:encoded><![CDATA[<p><img src="https://echofill.app/blog/images/chrome-autofill-not-filling-fields/thumb.jpg" alt=""></p>        <p>You click into the first box, Chrome offers your saved details, and you pick them. Name, email, phone and address pop in. Then you scroll down and everything else is still empty: the dropdowns, the checkboxes, the "Describe your request" box, the second page of the form. So you start typing anyway.</p>
        <p>Since I started using EchoFill, that's become rare for me, at least on the forms I fill again and again. It still happens when I open a brand-new form that asks for something I haven't filled in before. I type those few fields by hand once, save the form as its own profile, and from then on it's easy.</p>
        <p>This post covers the quick settings checks for when Chrome autofill isn't working at all, why it skips fields even when it is working, how to see what Chrome thinks each field is, and how to fill the fields it won't touch.</p>
        <h2 id="first-rule-out-the-settings-problems">First, rule out the settings problems</h2>
        <p>If Chrome offers nothing at all, the cause is usually one of these. Check them in order:</p>
        <ol><li><strong>Address autofill is switched off.</strong> Go to Settings → <strong>Autofill and passwords</strong> → <strong>Addresses and more</strong> and make sure <strong>Save and fill addresses</strong> is on.</li><li><strong>There's nothing saved yet,</strong> or the saved entry is missing the part you need. On the same page, open your address and fill in phone and email too. Chrome can only offer what it has.</li><li><strong>You're in a different Chrome profile or a guest or Incognito window.</strong> Each profile keeps its own addresses.</li><li><strong>Another extension is answering first.</strong> Password managers often put their own menu on name and address fields. Try the form with that extension paused.</li><li><strong>The site asked browsers not to fill.</strong> Some forms mark fields with <code>autocomplete="off"</code>. Chrome often fills address fields anyway, but sites sometimes go further and rename fields to avoid autofill entirely, and then Chrome has nothing to recognize.</li></ol>
        <p>If Chrome offers your details on the first field but the rest of the form stays empty, the settings are fine. That's the next section.</p>
        <h2 id="why-chrome-skips-fields-even-when-autofill-is-on">Why Chrome skips fields even when autofill is on</h2>
        <p><strong>Chrome only fills field types it recognizes.</strong> Its autofill was built for a short list: names, email, phone, postal addresses and payment cards. For each field it looks at the label, the <code>name</code> and <code>id</code> and the <code>autocomplete</code> attribute, and guesses which of those types it is. If it can't place the field in that list, it leaves it alone.</p>
        <p>Chrome's own developer blog shows the simplest case: a field whose only attributes are <code>type=text</code> and <code>name=n300</code>. Nothing in that tells Chrome what belongs there, so it <a href="https://developer.chrome.com/blog/devtools-autofill" rel="noopener" target="_blank">can't use it for structured autofill</a>. Real forms are full of fields like that.</p>
        <p>Here's what usually gets skipped, and why:</p>
        <div class="table-wrap"><table class="post-table"><thead><tr><th scope="col">Field on the form</th><th scope="col">Chrome autofill</th><th scope="col">Why</th></tr></thead><tbody><tr><td data-label="Field on the form">Name, email, phone, street, city, ZIP</td><td data-label="Chrome autofill">Usually fills</td><td data-label="Why">These are the types it was built for</td></tr><tr><td data-label="Field on the form">A field named <code>n300</code> or <code>field_7</code> with no clear label</td><td data-label="Chrome autofill">Skips</td><td data-label="Why">Nothing tells Chrome what it is</td></tr><tr><td data-label="Field on the form">"Describe your request", "Purpose of this ad", license numbers</td><td data-label="Chrome autofill">Skips</td><td data-label="Why">Not on Chrome's list of types, whatever you typed before</td></tr><tr><td data-label="Field on the form">Searchable or button-style dropdowns (Workday, React-Select)</td><td data-label="Chrome autofill">Skips</td><td data-label="Why">They aren't real <code>&lt;select&gt;</code> menus, so there's nothing for Chrome to set</td></tr><tr><td data-label="Field on the form">Checkboxes and radio buttons ("Yes, I'm authorized to work")</td><td data-label="Chrome autofill">Skips</td><td data-label="Why">Chrome doesn't save yes/no answers</td></tr><tr><td data-label="Field on the form">Step 2 of a multi-step form</td><td data-label="Chrome autofill">Only if each field is recognized</td><td data-label="Why">Every page starts over</td></tr><tr><td data-label="Field on the form">File uploads</td><td data-label="Chrome autofill">Skips</td><td data-label="Why">No browser lets autofill attach a file</td></tr></tbody></table></div>
        <p>None of this is a bug. Chrome's autofill is careful on purpose. A wrong guess in a payment form is worse than an empty box, so it only fills what it's sure about.</p>
        <p>I think Chrome is right to be this cautious. Some of what goes into forms is sensitive. If Chrome filled the wrong thing, or something leaked, or a user made a mistake, the blame would land on Chrome. I get why it doesn't want to take on that liability.</p>
        <h2 id="how-to-see-what-chrome-thinks-a-field-is">How to see what Chrome thinks a field is</h2>
        <p>If you're curious why one specific field didn't fill, Chrome will show you. This is the same check a developer would run.</p>
        <ol><li>On the form, press <code>Ctrl+Shift+I</code> (Windows) or <code>Cmd+Option+I</code> (Mac) to open DevTools.</li><li>Press <code>Ctrl+Shift+P</code> or <code>Cmd+Shift+P</code>, type <strong>autofill</strong>, and choose <strong>Show Autofill</strong>.</li><li>Click into the form and pick your saved address so Chrome fills it.</li><li>The <a href="https://developer.chrome.com/docs/devtools/autofill" rel="noopener" target="_blank">Autofill panel</a> lists each field Chrome detected, the value it predicted, and the value it actually put in.</li></ol>
        <p>Fields that aren't in the list are the ones Chrome never recognized. Typing them into your saved address won't help, because the problem is the field, not your data.</p>
        <h2 id="test-your-own-autofill-on-one-tricky-form">Test your own autofill on one tricky form</h2>
        <p>We built a free <a href="https://echofill.app/autofill-test.html">Autofill Test Form</a> with 18 of the field patterns that break form fillers: changing IDs, app-controlled inputs, button-style dropdowns, a second step that only appears after you click Next, and a few hard ones. It scores whatever tool you run on it, Chrome included.</p>
        <p>Try Chrome first. With an address saved, click into <strong>Full name</strong> and pick your details, then read the scorecard. Chrome can only help with the kinds of fields in the first row of the table above, so don't be surprised by a low number. Then click <strong>Clear everything</strong> and try any form filler you're thinking of installing, EchoFill included. Each field on the page says why tools fail it, so you'll see exactly where yours falls short before you rely on it for a real application.</p>
        <figure><img src="https://echofill.app/blog/images/chrome-autofill-not-filling-fields/chrome-vs-recorded.png" alt="Illustration of one sample form two ways: Chrome fills name, email, phone and address and skips the dropdown, radio, checkbox, free-text and step-2 fields, while a recorded profile fills all of them" width="1200" height="600" loading="lazy" decoding="async"><figcaption>Chrome fills field types it knows. A recorded form fills what you typed last time.</figcaption></figure>
        <h2 id="how-to-fill-the-fields-chrome-won-t-with-echofill">How to fill the fields Chrome won't, with EchoFill</h2>
        <p>The fix for "Chrome doesn't know what this field is" is a tool that doesn't need to know. EchoFill remembers what you typed into a specific form and puts it back next time. It's a free Chrome extension, and everything stays in your browser.</p>
        <ol><li><strong>Fill the form once by hand.</strong> Every field, including the dropdowns and checkboxes Chrome skipped.</li><li><strong>Click the EchoFill button → Record this form.</strong> Give the profile a name you'll recognize, like "Listing posts". EchoFill saves text, dropdown choices (including searchable and button-style menus), checkboxes and radio buttons. It never saves passwords, card numbers or Social Security numbers.</li><li><strong>Next time, click Autofill.</strong> EchoFill matches fields by their label, name and placeholder, so it still finds them when a site changes its hidden IDs. Leave <strong>Fill automatically next time</strong> checked and it fills as soon as the page opens on sites you approve.</li><li><strong>Check it and submit.</strong> If anything filled wrong, <strong>Undo</strong> puts every field back in one click. If you changed an answer, click <strong>Update</strong> to save the new version.</li></ol>
        <p>On the ad and listing forms I post over and over, every field fills. When a new site asks for something different, I fill it once by hand and record it as its own profile.</p>
        <div class="cta-inline"><b>Stop retyping the same answers.</b><a class="btn btn-primary" href="https://chromewebstore.google.com/detail/echofill/hejhcpofobcnifcgodjifdpipdfjdpmh">Add to Chrome, it's free</a></div>
        <p>Two limits, so you're not surprised. EchoFill can't attach files, because no extension can. And it doesn't fill rich-text editors (the boxes with a bold and italic toolbar) yet. Fields inside embedded frames and web components aren't supported in the current version either.</p>
        <h2 id="keep-chrome-s-autofill-for-what-it-s-good-at">Keep Chrome's autofill for what it's good at</h2>
        <p>Chrome's autofill is still the right tool for payment cards and passwords, where its security checks matter. EchoFill never records cards or passwords, so the two don't compete there.</p>
        <p>Addresses are different. I turned Chrome's address autofill off. EchoFill was already filling those fields well, I didn't see the need for both, and sometimes the two conflicted. If you'd rather keep both on, EchoFill fills only empty fields by default, so it won't overwrite what Chrome already put in.</p>
        <p>There's a longer side-by-side on the <a href="https://echofill.app/compare.html">EchoFill vs. Chrome autofill page</a>, and if job portals are your main pain, the <a href="https://echofill.app/blog/autofill-workday-applications.html">Workday guide</a> goes step by step.</p>
        <h2 id="frequently-asked-questions">Frequently asked questions</h2>
        <details><summary>Why does Chrome autofill not work on some websites?</summary>
        <p>Usually because the site's fields don't tell Chrome what they are. Chrome only fills names, contact details, addresses and payment cards, and only when it can recognize the field from its label or attributes. Sites with unusual field names, custom dropdowns or multi-step forms get partial fills or none.</p>
        </details>
        <details><summary>Why won't Chrome autofill fill dropdown menus?</summary>
        <p>Chrome can set a standard <code>&lt;select&gt;</code> menu when it recognizes the field, like State or Country. Many modern sites use custom menus built from buttons and lists instead, which Chrome can't operate. A form recorder like EchoFill opens the menu and picks the option by its visible text.</p>
        </details>
        <details><summary>Can I add custom fields to Chrome autofill?</summary>
        <p>No. Chrome's saved addresses have a fixed set of fields, and there's no way to add your own, like a license number or a standard answer. For those you need an extension that records what you typed on the form itself.</p>
        </details>
        <details><summary>Does autocomplete="off" stop Chrome from autofilling?</summary>
        <p>Not reliably. Chrome often ignores it on address fields, because users want those filled. That's why some sites rename fields instead, which also stops Chrome from recognizing them.</p>
        </details>
        <details><summary>Should I turn off Chrome autofill if I use a form filler?</summary>
        <p>You don't have to. Keep Chrome's password and payment card autofill either way. For addresses, it's personal preference: I switched Chrome's address autofill off because EchoFill already filled those fields and the two sometimes conflicted. If you keep both, EchoFill only fills fields that are still empty.</p>
        </details>
        <details><summary>Is it safe to use a form filler extension?</summary>
        <p>It depends on where the extension keeps your data. Check whether it needs an account, uploads what you type or sends it to an AI service. EchoFill stores everything locally in your browser with no account, and never records passwords, card numbers or Social Security numbers.</p>
        </details>
        <div class="news "><div class="news-copy"><b>Get new form-filling guides by email</b><p>One short email when we publish a new guide. No spam, unsubscribe anytime.</p></div><form class="news-form" action="https://buttondown.com/api/emails/embed-subscribe/echofill" method="post" target="_blank" data-news><label class="sr" for="nl-email-39">Email address</label><input id="nl-email-39" type="email" name="email" required placeholder="you@example.com" autocomplete="email"><input type="hidden" name="embed" value="1"><button class="btn btn-primary" type="submit">Subscribe</button><p class="news-ok" role="status" hidden>Almost done: check your inbox and click the confirmation link.</p><p class="news-fine">By subscribing you agree to our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p></form></div>]]></content:encoded></item>
    <item><title>How to stop retyping Workday job applications (without an AI tool)</title><link>https://echofill.app/blog/autofill-workday-applications.html</link><guid isPermaLink="true">https://echofill.app/blog/autofill-workday-applications.html</guid><pubDate>Fri, 09 Oct 2026 08:00:00 -0700</pubDate><description>Tired of retyping the same answers on every Workday portal? Fill each step in one click with no AI and nothing uploaded, plus what&#x27;s safe to autofill.</description><enclosure url="https://echofill.app/blog/images/autofill-workday-applications/thumb.jpg" type="image/jpeg" length="0"/><content:encoded><![CDATA[<p><img src="https://echofill.app/blog/images/autofill-workday-applications/thumb.jpg" alt=""></p>        <p>If you've applied to more than a handful of jobs this year, you know the routine. You find a role, click Apply, and land on a Workday portal that wants an account, your résumé, and then the same forty questions you answered yesterday for a different company. Name, address, phone, every job you've held with exact months, every degree, "How did you hear about us?", work authorization, sponsorship, relocation. Then you do it again tomorrow.</p>
        <p>I've been through more job searches than I'd like, and a lot of them ran through Workday. First name, last name, phone, email, address, then a description for every role I'd held. None of it was hard. It was just slow. On a lot of applications, more than half my time went to typing details I'd already typed somewhere else, and that adds up fast when you're applying to several jobs in a day. My wife has complained about the exact same thing. That's exactly the kind of time EchoFill was built to give back.</p>
        <p>This guide covers why Workday works this way, which parts you can safely autofill, which parts you shouldn't, and how to set things up once so every future application takes minutes instead of half an hour.</p>
        <h2 id="why-workday-makes-you-start-from-zero-every-time">Why Workday makes you start from zero every time</h2>
        <p>Workday isn't one website. Each employer runs its own copy, usually at an address like <code>company.wd5.myworkdayjobs.com</code>. Your account, your uploaded résumé and your answers live inside that one company's copy. Apply somewhere else and you're a stranger again, even though the pages look identical.</p>
        <p>The "Autofill with résumé" button doesn't save you much either. It reads your résumé file and guesses which text goes where. Job titles land in the company field, months go missing, bullet points get merged into one paragraph, and you spend as long fixing the guesses as you would have spent typing.</p>
        <p>So the problem isn't really typing speed. It's that <strong>the same answers have to be entered into dozens of separate systems that can't talk to each other.</strong> Your browser has to remember them, because nobody else will.</p>
        <h2 id="what-chrome-s-built-in-autofill-does-and-doesn-t-cover">What Chrome's built-in autofill does (and doesn't) cover</h2>
        <p>Chrome will fill your name, email, phone and address if the fields are labeled in a standard way. On Workday that covers roughly the first screen. Everything after it is out of reach:</p>
        <div class="table-wrap"><table class="post-table"><thead><tr><th scope="col">Workday step</th><th scope="col">Chrome autofill</th><th scope="col">Remembered answers (EchoFill)</th></tr></thead><tbody><tr><td data-label="Workday step">My Information (name, address, phone)</td><td data-label="Chrome autofill">Mostly</td><td data-label="Remembered answers (EchoFill)">Yes</td></tr><tr><td data-label="Workday step">"How did you hear about us?" and other dropdowns</td><td data-label="Chrome autofill">No</td><td data-label="Remembered answers (EchoFill)">Yes, including Workday's searchable menus</td></tr><tr><td data-label="Workday step">My Experience (jobs, dates, descriptions)</td><td data-label="Chrome autofill">No</td><td data-label="Remembered answers (EchoFill)">Yes, once recorded</td></tr><tr><td data-label="Workday step">Education</td><td data-label="Chrome autofill">No</td><td data-label="Remembered answers (EchoFill)">Yes</td></tr><tr><td data-label="Workday step">Application Questions (authorization, sponsorship, relocation)</td><td data-label="Chrome autofill">No</td><td data-label="Remembered answers (EchoFill)">Yes, but review each one</td></tr><tr><td data-label="Workday step">Voluntary Disclosures / Self Identify</td><td data-label="Chrome autofill">No</td><td data-label="Remembered answers (EchoFill)">We suggest you answer these yourself</td></tr><tr><td data-label="Workday step">Résumé upload</td><td data-label="Chrome autofill">No</td><td data-label="Remembered answers (EchoFill)">No: browsers don't let extensions attach files</td></tr></tbody></table></div>
        <h2 id="the-three-parts-you-should-never-autofill-blindly">The three parts you should never autofill blindly</h2>
        <p>Speed matters, but a wrong answer on a job application costs more than five minutes of typing. Before you automate anything, know where to slow down:</p>
        <ol><li><strong>Legal attestations.</strong> Questions like "Are you legally authorized to work in this country?" and "Will you now or in the future require sponsorship?" usually have the same answer every time, so autofill is fine, but <em>read each one</em>. Companies phrase them differently, and a question that is worded in the negative can flip what "Yes" means.</li><li><strong>Voluntary self-identification.</strong> Gender, race and ethnicity, veteran status and disability questions are optional and private. Decide each time whether you want to answer, rather than letting a tool decide for you.</li><li><strong>Anything role-specific.</strong> Salary expectations, start date, "Why do you want to work here?" and portfolio links change from job to job. Leave them blank in your saved answers so you're forced to think about them.</li></ol>
        <p>The same goes for experience write-ups when a role is unusual. A saved description of your past jobs is a great starting point, but if the posting asks for something specific, copying in the same text won't make you stand out. That part is your call, and it should be. Let the tool handle the admin so you have time for the answers that actually get you noticed.</p>
        <figure><img src="https://echofill.app/blog/images/autofill-workday-applications/workday-steps.png" alt="Workday&#x27;s application steps, with the steps that are safe to fill in one click marked in green and the steps to review yourself marked in amber" width="1200" height="580" loading="lazy" decoding="async"><figcaption>What to fill in one click, and what to review yourself</figcaption></figure>
        <h2 id="how-to-fill-workday-applications-in-one-click-with-echofill">How to fill Workday applications in one click with EchoFill</h2>
        <p>EchoFill is a free Chrome extension that remembers what you type into a form and fills it back in next time. It works on what's already on the page, in your browser, so there's no résumé parsing and nothing is sent to an AI service.</p>
        <ol><li><strong>Fill one application by hand, carefully.</strong> Pick a Workday application you were going to submit anyway and fill in every step. Take your time: these become your saved answers.</li><li><strong>Record each step.</strong> On each page, before you click Save and Continue, click the EchoFill button → <strong>Record this form</strong>. Name the profile something like "Workday standard answers". Leave <strong>Fill automatically next time</strong> checked if you want that portal filled as soon as a page opens. EchoFill saves text fields, dropdown choices (including Workday's searchable lists), checkboxes and radio buttons, and it never saves passwords. Skip recording the Voluntary Disclosures and Self Identify steps so those always stay your call.</li><li><strong>On the next company's Workday, click Autofill.</strong> Open the new application, click EchoFill → <strong>Autofill</strong> on each step, and pick your Workday profile. Fields are matched by their labels, and Workday's standard fields use the same labels at every company, so "Legal Name – First Name" finds your first name even though it's a completely different site.</li><li><strong>Review, adjust, submit.</strong> Check the attestation questions, answer the self-identification questions yourself, and update anything role-specific. If something filled wrong, one click on <strong>Undo</strong> restores the page.</li></ol>
        <p>Here's what it looked like when I used it on a real Workday application. When I opened a page with fields I'd filled before, EchoFill filled them in as soon as the page loaded. The biggest time saver wasn't my name and address. It was the work history: every role over the years, each with a description, which is the part that takes longest to type. Where it fell short was tailored answers. For roles that were a bit unusual, the same saved text wasn't the best answer, and I rewrote it by hand. My wife uses it for her applications now too, and she likes it a lot. Each fill only saves a few minutes, but across dozens of applications that's hours back for the parts that matter.</p>
        <div class="cta-inline"><b>Stop retyping the same answers.</b><a class="btn btn-primary" href="https://chromewebstore.google.com/detail/echofill/hejhcpofobcnifcgodjifdpipdfjdpmh">Add to Chrome, it's free</a></div>
        <h3 id="keep-one-profile-per-version-of-you">Keep one profile per "version" of you</h3>
        <p>If you're applying to two kinds of roles, say product management and operations, keep two profiles with different summaries, titles and answers. The free plan includes three profiles, which covers most job searches. If you need more, Pro removes the limit.</p>
        <h3 id="when-a-field-doesn-t-fill">When a field doesn't fill</h3>
        <p>Workday occasionally changes how a particular field is built. If one stays empty, type it once and record the step again with <strong>Update</strong>. EchoFill keeps your other answers and adds the new one.</p>
        <h2 id="a-quick-checklist-before-you-hit-submit">A quick checklist before you hit Submit</h2>
        <ul><li>Your name and contact details match your résumé exactly</li><li>Job dates are in the right format (Workday usually wants month and year)</li><li>Attestation questions say what you mean, especially any worded in the negative</li><li>Self-identification answered the way <em>you</em> chose</li><li>Salary, start date and cover letter fields updated for this role</li><li>The right résumé file is attached (EchoFill can't attach files for you)</li></ul>
        <h2 id="frequently-asked-questions">Frequently asked questions</h2>
        <details><summary>Is it safe to use an autofill extension on job applications?</summary>
        <p>It depends on where your data goes. Many AI job tools upload your résumé and answers to their servers to generate responses. EchoFill stores your answers only in your browser on your own computer. There's no EchoFill account and no server copy. You can read exactly what it stores in our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p>
        </details>
        <details><summary>Will autofilling get my application flagged?</summary>
        <p>Workday sees the same thing it sees when you type: values in fields. EchoFill doesn't submit anything for you, and it doesn't click through pages on its own. You still review and submit every application yourself.</p>
        </details>
        <details><summary>Does EchoFill work on Greenhouse, Lever and iCIMS too?</summary>
        <p>EchoFill isn't tied to a list of supported sites. It matches fields by their labels, so the same approach applies: record a step once on each portal, then check the first fill before you rely on it. In my experience the limit is less about the portal and more about the question. Standard details fill easily anywhere. Answers that need tailoring to one specific role still need you.</p>
        </details>
        <details><summary>Do I need to pay for this?</summary>
        <p>No. The free plan has unlimited fills and three saved profiles. Pro ($2.99/month, $19.99/year or $29.99 once) adds unlimited profiles and fills fields on sites you've never recorded by understanding what each field asks for.</p>
        </details>
        <div class="news "><div class="news-copy"><b>Get new form-filling guides by email</b><p>One short email when we publish a new guide. No spam, unsubscribe anytime.</p></div><form class="news-form" action="https://buttondown.com/api/emails/embed-subscribe/echofill" method="post" target="_blank" data-news><label class="sr" for="nl-email-41">Email address</label><input id="nl-email-41" type="email" name="email" required placeholder="you@example.com" autocomplete="email"><input type="hidden" name="embed" value="1"><button class="btn btn-primary" type="submit">Subscribe</button><p class="news-ok" role="status" hidden>Almost done: check your inbox and click the confirmation link.</p><p class="news-fine">By subscribing you agree to our <a href="https://echofill.app/privacy.html">privacy policy</a>.</p></form></div>]]></content:encoded></item>
  </channel>
</rss>
