Skip to content
Product block

Import From URL Form

The import path for a file that is already on the internet, which does not need to travel through the browser at all.

178 linesNo dependenciesAdded 9 Sept 2026
  • import
  • url
  • upload
  • remote
  • form

What's included

  • components/import-from-url-form.tsx
  • No runtime dependencies

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add import-from-url-form

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Start a page with this section — add more, order them, and leave with the page source.

Preview

Import from a link

A file that already lives at a URL does not need to be downloaded to a laptop and uploaded again. The server fetches it, which also survives the tab being closed.

Must be publicly reachable. Signed links work; a login page does not.

Detected from the response, not the extension. Override only if it guesses wrong.

Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.

Source

components/import-from-url-form.tsx
'use client'

/**
 * <ImportFromUrlForm> — The import path for a file that is already on the internet, which does not need to travel through the browser at all.
 *
 * A file that already lives at a URL does not need to travel down to a
 * laptop and back up again. The layout problem is that the obvious wrong
 * answer — a drop zone — cannot express this at all: there is no file to
 * drop, and the operation is a server-side fetch that outlives the tab.
 *
 * So this is a two-field form rather than a target, and the second field
 * matters more than it looks. Format is detected from the response content
 * type rather than from the extension, which is stated in the hint because
 * the reader is about to wonder why the field is pre-filled and editable.
 *
 * The URL hint names the failure everyone hits: a link behind a login
 * returns an HTML sign-in page with a 200, and a naive importer cheerfully
 * parses it as the data. Saying "signed links work; a login page does not"
 * in advance is cheaper than the error message that would otherwise be
 * needed.
 *
 * Accessibility: labels associated by `htmlFor`/`id` with the constraint
 * hints wired through `aria-describedby`, and a `role="status"` region
 * present and empty from first paint. The region matters more here than on
 * most forms because a server-side fetch takes real time — the pending state
 * is the only feedback there is, and it has to be announced rather than only
 * shown on the button.
 *
 * The demo defaults to `idle`; the scaffold's submit sets `pending` before
 * awaiting, so the disabled button and the status line both reflect a real
 * in-flight state.
 */

import * as React from 'react'

export interface ImportFromUrlFormProps {
  heading?: string
  intro?: string
  submitLabel?: string
  /** Called with the collected values. Resolve to accept, throw to reject. */
  onSubmit?: (values: Record<string, string>) => Promise<void> | void
  className?: string
}

type Status = 'idle' | 'pending' | 'done' | 'error'

/*
  A typed array rather than `as const`. With `as const` the entries have
  different shapes - some carry a hint, some do not - so `field.hint` is a
  type error on the members that lack it, and the `'hint' in field` dance
  needed to work around that is worse than declaring the field optional once.
*/
interface ImportFromUrlFormField {
  name: string
  label: string
  type: string
  hint?: string
}

const FIELDS: ImportFromUrlFormField[] = [
  { name: "url", label: "File URL", type: "url", hint: "Must be publicly reachable. Signed links work; a login page does not." },
  { name: "format", label: "Format", type: "text", hint: "Detected from the response, not the extension. Override only if it guesses wrong." },
]

export function ImportFromUrlForm({
  heading = "Import from a link",
  intro = "A file that already lives at a URL does not need to be downloaded to a laptop and uploaded again. The server fetches it, which also survives the tab being closed.",
  submitLabel = "Fetch and import",
  onSubmit,
  className,
}: ImportFromUrlFormProps) {
  /*
    Per-instance prefix for every id this block emits.

    The literals these replaced were a latent duplicate the moment the
    block appeared twice on one document, and `aria-labelledby` on a
    duplicated id resolves to the first match -- so the second copy was
    labelled by the first copy's heading. Client component, so `useId` is
    the right tool.
  */
  const uid = React.useId()

  const [status, setStatus] = React.useState<Status>('idle')
  const [message, setMessage] = React.useState('')

  async function handleSubmit(event: React.FormEvent<HTMLFormElement>) {
    event.preventDefault()
    const data = new FormData(event.currentTarget)
    const values = Object.fromEntries(
      FIELDS.map((field) => [field.name, String(data.get(field.name) ?? '')]),
    )

    setStatus('pending')
    try {
      await onSubmit?.(values)
      setStatus('done')
      setMessage('Thanks — that came through.')
    } catch (error) {
      setStatus('error')
      setMessage(error instanceof Error ? error.message : 'That did not go through.')
    }
  }

  return (
    <section
      aria-labelledby={`${uid}-import-from-url-form-heading`}
      className={`w-full bg-background px-6 py-16 ${className ?? ''}`}
    >
      <div className="mx-auto max-w-md rounded-xl border border-border bg-card p-8 shadow-sm">
        <h2
          id={`${uid}-import-from-url-form-heading`}
          className="text-xl font-semibold tracking-tight text-card-foreground"
        >
          {heading}
        </h2>
        <p className="mt-2 text-sm text-muted-foreground">{intro}</p>

        <form onSubmit={handleSubmit} className="mt-6 space-y-4">
          {FIELDS.map((field) => (
            <div key={field.name}>
              {/*
                htmlFor / id rather than a wrapping label, so the hint can
                sit outside the label and still be announced — that is what
                aria-describedby is for.
              */}
              <label
                htmlFor={`${uid}-import-from-url-form-${field.name}`}
                className="block text-sm font-medium text-foreground"
              >
                {field.label}
              </label>
              <input
                id={`${uid}-import-from-url-form-${field.name}`}
                name={field.name}
                type={field.type}
                required
                aria-describedby={field.hint ? `${uid}-import-from-url-form-${field.name}-hint` : undefined}
                className="mt-1.5 w-full rounded-md border border-input bg-background px-3 py-2 text-sm text-foreground placeholder:text-muted-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring"
              />
              {field.hint ? (
                <p
                  id={`${uid}-import-from-url-form-${field.name}-hint`}
                  className="mt-1 text-xs text-muted-foreground"
                >
                  {field.hint}
                </p>
              ) : null}
            </div>
          ))}

          <button
            type="submit"
            disabled={status === 'pending'}
            className="w-full rounded-md bg-primary px-4 py-2 text-sm font-medium text-primary-foreground transition-opacity hover:opacity-90 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:opacity-60"
          >
            {status === 'pending' ? 'Working…' : submitLabel}
          </button>

          {/*
            The live region is always in the DOM and starts empty. A region
            mounted at the moment it gets text is frequently not announced —
            the assistive tech never saw it become live.
          */}
          <p
            role="status"
            aria-live="polite"
            className={`min-h-5 text-sm ${
              status === 'error' ? 'text-destructive' : 'text-muted-foreground'
            }`}
          >
            {message}
          </p>
        </form>
      </div>
    </section>
  )
}

Before you paste

  • Styling is Tailwind utility classes on semantic tokens (bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.
  • Nothing to install. No component library, no icon package.
  • Every prop has a default, so it renders standalone before you wire it up.

Where it goes

Drop it at components/import-from-url-form.tsx and import it where you need the section:

import { ImportFromUrlForm } from '@/components/import-from-url-form'

Customize

2 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.

Props

Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.

PropTypeDefault
headingstring"Import from a link"
introstring—
submitLabelstring"Fetch and import"
onSubmitCalled with the collected values. Resolve to accept, throw to reject.(values: Record<string, string>) => Promise<void> | void—
classNamestring—

Not using React?

The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.

This block is interactive. The markup below is its initial state with the event handlers stripped — you will need to re-wire the behaviour in your framework.

import-from-url-form.html
<!--
  Import From URL Form — markup from the Hoverlab catalog.

  This is the block rendered once to HTML and wrapped as a component
  file. It is not a port of the React source: the Tailwind classes carry
  the design, which is the part that took the work, and they are the same
  in every framework.

  This block is interactive in React and the handlers are NOT here.
  Buttons, toggles and menus render in their initial state and do
  nothing until you wire them up.
-->
<section aria-labelledby="_R_0_-import-from-url-form-heading" class="w-full bg-background px-6 py-16 ">
  <div class="mx-auto max-w-md rounded-xl border border-border bg-card p-8 shadow-sm">
    <h2 id="_R_0_-import-from-url-form-heading" class="text-xl font-semibold tracking-tight text-card-foreground">Import from a link</h2>
    <p class="mt-2 text-sm text-muted-foreground">A file that already lives at a URL does not need to be downloaded to a laptop and uploaded again. The server fetches it, which also survives the tab being closed.</p>
    <form class="mt-6 space-y-4">
      <div>
        <label for="_R_0_-import-from-url-form-url" class="block text-sm font-medium text-foreground">File URL</label>
        <input id="_R_0_-import-from-url-form-url" type="url" required="" aria-describedby="_R_0_-import-from-url-form-url-hint" class="mt-1.5 w-full rounded-md border border-input bg-background px-3 py-2 text-sm text-foreground placeholder:text-muted-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring" name="url" />
        <p id="_R_0_-import-from-url-form-url-hint" class="mt-1 text-xs text-muted-foreground">Must be publicly reachable. Signed links work; a login page does not.</p>
      </div>
      <div>
        <label for="_R_0_-import-from-url-form-format" class="block text-sm font-medium text-foreground">Format</label>
        <input id="_R_0_-import-from-url-form-format" type="text" required="" aria-describedby="_R_0_-import-from-url-form-format-hint" class="mt-1.5 w-full rounded-md border border-input bg-background px-3 py-2 text-sm text-foreground placeholder:text-muted-foreground focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring" name="format" />
        <p id="_R_0_-import-from-url-form-format-hint" class="mt-1 text-xs text-muted-foreground">Detected from the response, not the extension. Override only if it guesses wrong.</p>
      </div>
      <button type="submit" class="w-full rounded-md bg-primary px-4 py-2 text-sm font-medium text-primary-foreground transition-opacity hover:opacity-90 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring disabled:opacity-60">Fetch and import</button>
      <p role="status" aria-live="polite" class="min-h-5 text-sm text-muted-foreground"></p>
    </form>
  </div>
</section>
  • This is rendered HTML, not a translation of the React source. The Tailwind classes carry the design and work in any framework.
  • It is one frame: the component in its initial state, with no props applied beyond the defaults.
  • This block is interactive in React — toggles, menus or form state. None of that survives here; the markup is the closed/default state and the handlers are gone. Re-wire them in your own framework.
  • Requires Tailwind, and the design tokens the classes reference (bg-card, text-muted-foreground, and so on). The template ZIPs ship a globals.css that defines them.

What each framework gets across the whole catalog — effects convert properly; this rung is markup.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt

Used in these pages

Want the whole screen instead of this one section? Open a page and copy it entire.

6 more blocks in File Upload

All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.

Browse File Upload

Shipping one commercially

Copying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.

  • A commercial licence for everything in the catalog
  • Unlimited bundle exports, in Vue, Svelte and Tailwind
  • One payment — no subscription, nothing to renew
Pro — $79 once

More File Upload blocks

View category
Open the full page for this block

Drag & Drop Upload

Dropzone with per-file progress and a drag counter that fixes the flicker every naive dragleave handler produces.

File Upload219 lines1 dep
Open the full page for this block

Upload Progress List

The list that follows the dropzone: complete, uploading, queued and failed rows with cancel and retry — because hiding the failure is the classic upload bug.

File Upload171 lines1 dep
Open the full page for this block

Resumable Large Upload

One big file on a connection that will drop: a bar allowed to go backwards when a chunk is retried, a time estimate that is a range or nothing, and a promise about closing the tab made before it is needed.

File Upload237 lines1 dep
Open the full page for this block

CSV Column Mapper

The screen between "file uploaded" and "data imported": source columns mapped to schema fields, with a sample value under each and required fields blocking the button.

File Upload280 lines1 dep
Open the full page for this block

Avatar Crop & Upload

Framing a profile photo with keyboard-operable zoom and position, showing what gets trimmed rather than hiding it behind the mask.

File Upload268 lines1 dep
Open the full page for this block

Upload Requirements Form

An upload form that states the constraints before the file is chosen, rather than rejecting it after a two-minute transfer.

File Upload184 linesNo deps