The Complete Guide to HiBid CSV Imports (2026)

HiBid CSV imports require a specific column structure, exact photo naming conventions, and clean character encoding to work. Getting any of these wrong means a failed upload and hours of rework. This guide covers the exact format HiBid expects, every common error and how to fix it, and how to automate the entire process so a 500-lot catalog goes from photos to published listing in under 20 minutes instead of an entire afternoon.

Last updated: April 2026

HiBid CSV Column Structure

HiBid expects these columns in your CSV. The Lead and Description fields are where most of your catalog value lives -- everything else is metadata.

The Lead Field -- Your Most Important 80 Characters

The Lead is the first thing bidders see in search results, thumbnail grids, and email notifications. It's the difference between someone clicking into your lot or scrolling past it. A Lead that just says "Vase" is invisible. A Lead that says "Rookwood Standard Glaze Vase, Shirayamadani, 1903" stops a collector mid-scroll.

What works:

• Lead with the maker or brand name -- bidders search by maker
• Include the material or key identifier -- "Sterling," "14K," "Oil on Canvas"
• Add the date or era if known -- "c.1920," "Mid-Century," "Depression Era"
• Skip filler words -- "Beautiful," "Nice," "Vintage" waste your 80 characters

Examples that sell vs. examples that don't:

Every word in a Lead should help a bidder decide whether to click. If a word doesn't add identification value, cut it.

The Description Field

HiBid descriptions support basic HTML. Use paragraph tags for readability -- a wall of unformatted text discourages reading and reduces bids.

<p>Rookwood Pottery Standard Glaze vase, shape 907C,
artist-signed by Kataro Shirayamadani, dated 1903.</p>
<p>Floral decoration with warm amber and brown tones
typical of the Standard Glaze line. Light crazing to
glaze near rim, small professionally stabilized chip
to base edge.</p>
<p>Height: 8.5 inches</p>

Stick to <p>, <br>, <b>, and <i> tags. Avoid tables, divs, and inline styles -- complex HTML may not render correctly in HiBid's listing display.

Description structure that works for estate auctions:

1. Identification line -- what the item IS (maker, type, material, date)
2. Details -- decoration, markings, provenance, notable features
3. Condition -- honest assessment with appropriate hedging language
4. Measurements -- height, width, depth as relevant

This structure matches how experienced auction house catalogers write because it front-loads the information that drives bidding decisions. For jewelry, lead with metal type and setting style. For ceramics, the backstamp identification is critical. For furniture, period and wood type come first.

Photo Naming Conventions

HiBid matches photos to lots by filename. This is where the most preventable import failures happen.

The Required Format

{LotNumber}-{PhotoSequence}.jpg

Examples:

• 1-1.jpg -- Lot 1, primary photo (becomes the thumbnail)
• 1-2.jpg -- Lot 1, second photo
• 1-3.jpg -- Lot 1, third photo
• 2-1.jpg -- Lot 2, primary photo

Rules That Will Break Your Import If Ignored

• The -1 photo becomes the thumbnail. This should always be your best front-facing hero shot. Backstamps and detail shots go in positions 2 and up.
• Lot numbers in filenames must exactly match your CSV. If the CSV says lot 1 and the photo is named 001-1.jpg, HiBid won't match them. This is the single most common import failure.
• JPEG and PNG accepted. HiBid supports .jpg, .jpeg, and .png files. HEIC files from iPhones may be auto-converted during import, but it's safer to convert to JPEG before uploading.
• Pre-resize your photos. Full-resolution camera photos (4000x6000px, 8-12MB each) take significantly longer to upload and process than resized versions. Pre-resizing to 1024px on the long edge keeps files around 150-200KB while maintaining enough detail for online viewing. For large uploads, this makes a real difference in processing time.
• No spaces in filenames. Lot 1-1.jpg may cause issues. 1-1.jpg is clean.

The Five Mistakes That Kill Most HiBid Imports

1. Leading zeros mismatch. Your CSV says lot 1. Your photos say 001-1.jpg. HiBid sees these as different lots. Pick a numbering scheme and use it everywhere.
2. Wrong separator. HiBid's convention uses a dash (1-1.jpg). Using an underscore or other separator may prevent photo-to-lot matching.
3. Mixed case extensions. .JPG from your camera vs .jpg in the CSV reference. Some systems are case-sensitive.
4. Duplicate lot numbers. Two rows in the CSV with the same lot number. This happens when lots get split or renumbered during the sorting process and the CSV doesn't get updated.
5. Special characters in the CSV. Curly quotes, em dashes, and accented characters from copy-pasting descriptions can corrupt CSV parsing entirely. Replace curly quotes with straight quotes, em dashes with regular dashes, and accented characters with ASCII equivalents. Or use a tool that sanitizes automatically.

Common HiBid Import Errors and Fixes

"Invalid column count"

Your CSV has inconsistent columns across rows. This usually means a description contains an unescaped comma that split a field into two columns. Open the file in a text editor (not Excel -- Excel hides CSV formatting issues) and check that every row has the same number of delimiters. The fix: make sure every field containing commas is wrapped in double quotes.

"Duplicate lot number"

Two rows share the same lot number. Search your CSV for the duplicate. This often happens when a lot was split during cataloging -- the original lot and the new lot ended up with the same number. Renumber one of them.

"Invalid characters in description"

Character encoding mismatch. HiBid expects UTF-8 but your file might be saved as Windows-1252 or Latin-1 if you edited it in Excel on Windows. Re-save as UTF-8 in a text editor, or replace the problem characters:

• Curly quotes \u201c \u201d with straight quotes "
• Em dashes \u2014 with regular dashes -
• Smart apostrophes \u2019 with standard apostrophes '

"Photo not found for lot"

The lot number in your CSV doesn't match any photo filename. Check for leading zero mismatches first -- that's the most common cause.

The Real Cost of Manual CSV Creation

Building a HiBid CSV by hand for a 500-lot estate sale means:

• Writing the CSV: 3-4 hours formatting a spreadsheet, mapping columns, escaping special characters
• Renaming photos: 1-2 hours renaming 1,500-3,000 photos from camera names (IMG_4521.jpg) to HiBid format (1-1.jpg)
• Fixing errors: 30-60 minutes debugging import failures, fixing mismatches, re-uploading
• Total: 5-7 hours of work that adds zero value to your catalog

That's time you're not spending on consignment calls, client relationships, or running the actual auction. At $25/hour equivalent cost, a 500-lot manual CSV costs $125-175 in labor -- for formatting work, not even for writing the descriptions.

Automating the Entire Process

The technical requirements for a clean HiBid import -- column mapping, photo naming, character sanitization, Lead generation, duplicate detection -- are all deterministic problems. They don't require human judgment. They require a tool that knows HiBid's format.

What a proper automation tool handles:

1. Column mapping -- formats your lot data into HiBid's exact column structure
2. Photo sequencing -- orders photos correctly so your best shot becomes the thumbnail, with up to 5 images per lot
3. Character sanitization -- strips or replaces characters that break CSV parsing before you ever see an error
4. Lead extraction -- generates a concise, searchable title from the full description
5. Validation -- catches duplicate lot numbers, missing photos, and format issues before you attempt the upload
6. Pre-sizing -- photos resized to web-appropriate dimensions so HiBid's upload processor doesn't choke

Gavelist handles all of this in a single export step. After AI generates your descriptions from your photos -- analyzing every angle including backstamps, maker marks, and condition details -- the HiBid export produces a correctly formatted CSV with up to 5 image references per lot, properly sequenced. The entire flow from raw photos to HiBid-ready catalog takes under 20 minutes for a 500-lot estate at $0.15 per lot.

Step-by-Step: Manual HiBid Upload

If you're building the CSV yourself:

1. Log into HiBid Auctioneer Console
2. Navigate to your auction event
3. Click Import Lots
4. Select CSV Upload
5. Upload your CSV file
6. Map columns if prompted (HiBid auto-detects standard formats but may ask for confirmation)
7. Review imported lots for accuracy -- spot-check at least 10 lots across different categories
8. Navigate to Photos
9. Upload your photo folder (ZIP for large batches)
10. Verify photos matched to correct lots -- check thumbnail alignment
11. Preview your catalog
12. Publish

Time estimate: 5-7 hours for a 500-lot estate (including description writing, CSV formatting, photo renaming, and error fixing).

Step-by-Step: Automated HiBid Upload with Gavelist

1. Upload your estate photos to Gavelist (drag and drop, all formats accepted)
2. Sort into lots -- Gavelist auto-detects lot numbering from filenames, or use the conveyor belt interface for manual sorting
3. Run AI descriptions -- every photo in every lot gets analyzed across 18 item categories
4. Review the AI output and make any adjustments
5. Click Export > HiBid
6. Download the CSV
7. Upload to HiBid and publish

Time estimate: 15-20 minutes for a 500-lot estate. Description generation runs at roughly 10 seconds per lot with concurrent processing. Export itself takes seconds.

Tips From Running Thousands of HiBid Imports

These are lessons from processing thousands of lots through HiBid, not theoretical best practices:

• Test with 10 lots first. Before uploading a 500-lot CSV, test the format with a small batch. Finding a column mapping error on lot 10 is annoying. Finding it on lot 450 is a lost afternoon.

• Always keep your original photos. Before any renaming or resizing, back up the originals. If an import fails and you've already overwritten your source files, you're starting from scratch.

• Pre-resize before uploading to HiBid. HiBid re-processes every image server-side. Full-resolution photos (4000x6000px, 8MB each) take significantly longer to process than 1024px versions (150KB each). For a 1,000-photo upload, pre-resizing can save 30-60 minutes of HiBid server processing time. Your bidders are viewing on screens, not printing posters -- 1024px is more than enough.

• Pick a lot numbering scheme and never deviate. Numeric (1, 2, 3) or zero-padded (001, 002, 003) or alphanumeric (1A, 1B, 2A) -- it doesn't matter which, as long as your CSV and your photo filenames use the same one. Mixing schemes within a single auction is the fastest way to generate "photo not found" errors.

• Check your CSV in a text editor, not Excel. Excel silently reformats dates, strips leading zeros from lot numbers, and converts long numbers to scientific notation. Open your CSV in Notepad, VS Code, or any plain text editor before uploading to HiBid. If lot 001 shows up as 1 in Excel, your photos won't match.

Frequently Asked Questions

What CSV format does HiBid require? HiBid accepts standard CSV files (comma-separated values) with specific columns: Lot Number, Lead (title), Description, Category, Condition, Starting Bid, Reserve, and up to 5 image references. All text fields containing commas must be wrapped in double quotes. Files should be saved as UTF-8 encoding.

How do I name photos for HiBid import? Use the format {LotNumber}-{PhotoSequence}.jpg. For example, lot 1's primary photo is 1-1.jpg, its second photo is 1-2.jpg. The first photo becomes the listing thumbnail. Lot numbers must exactly match your CSV. JPEG and PNG formats are supported.

What's the fastest way to create a HiBid catalog? AI cataloging tools like Gavelist generate HiBid-ready CSVs directly from your photos. Upload your estate photos, let AI generate descriptions across 18 item categories, then export to HiBid format with one click. A 500-lot estate takes about 15-20 minutes total versus 5-7 hours manually.

Why does HiBid say "photo not found" for my lots? The lot number in your CSV doesn't match the lot number in your photo filename. The most common cause is a leading zeros mismatch -- your CSV says lot 1 but your photo is named 001-1.jpg. HiBid treats these as different lots.

How many photos can I upload per lot on HiBid? HiBid supports multiple photos per lot. Gavelist's HiBid export includes up to 5 image references per lot, sequenced so your best photo appears as the thumbnail.

Can I use HTML in HiBid descriptions? Yes, but keep it simple. HiBid supports <p>, <br>, <b>, and <i> tags. Avoid tables, divs, and inline styles -- complex HTML may not render correctly in HiBid's listing display.

How much does it cost to automate HiBid imports? Gavelist's HiBid export is included with every plan. Pay-as-you-go pricing is $0.15 per lot with no monthly commitment. A 500-lot estate costs $75 total -- compared to $125-175 in labor costs for manual CSV creation and photo renaming.

Shopping for an AI cataloging tool that exports to HiBid? See our guide to evaluating AI auction description software.

Need help with your first HiBid import? Call Ben at (412) 580-7398 -- I'll walk you through it.