The four ways to import coordinates into AutoCAD
There are four practical routes for turning a list of coordinates into points in a drawing. Which one makes sense depends on how many points you have, which AutoCAD product you use, and how much time you want to spend preparing the data.
| Method | Best for | Pros | Cons |
|---|---|---|---|
| Manual entry | 1-5 points | No preparation, works everywhere | Slow, error-prone, impractical beyond a handful of points |
| Script file (.scr) | 10-1,000+ points in vanilla AutoCAD | Fast once built, works in AutoCAD LT | Requires spreadsheet formula work; no labels without extra effort |
| Civil 3D point import | Survey point files (PNEZD) | Native workflow, keeps point numbers and descriptions | Requires Civil 3D, not plain AutoCAD or LT |
| DXF import | Any point count, any AutoCAD product | Points arrive as real geometry on defined layers, labels included | Needs a tool that can generate the DXF |
Method 1: Manual entry with the POINT command
For a small handful of coordinates, the simplest route is typing them in. Start the POINT command and enter each coordinate as an X,Y pair - in survey terms, that is easting first, then northing, matching AutoCAD's X-then-Y convention.
There is one classic trap here. With Dynamic Input enabled (the default in modern AutoCAD), coordinates you type are treated as relative to the last point rather than absolute positions in the drawing. To force an absolute coordinate with Dynamic Input on, prefix the entry with a hash - for example #530029,180380. Alternatively, turn Dynamic Input off (the DYNMODE setting or the status bar toggle) and typed coordinates are absolute again.
Manual entry is fine for two or three points. Beyond that, transcription errors creep in fast - a single swapped digit in a six-figure easting moves a point by tens or hundreds of metres, and you will not necessarily notice until something fails to line up on site.
Method 2: Script files built from a spreadsheet
The traditional bulk method in plain AutoCAD is a script file - a plain text file with a .scr extension containing AutoCAD commands, one instruction per line. You build a column in your spreadsheet that assembles a POINT command for each row, for example a formula that produces POINT 530029.12,180380.45, then copy that column into a text file, save it as a .scr, and run it with the SCRIPT command.
This works, and it works in AutoCAD LT as well. But it has real friction: you have to get the spreadsheet formula exactly right, watch out for stray blank lines and trailing spaces (scripts are unforgiving about whitespace), remember the Dynamic Input behaviour described above, and if you also want each point labelled with its name or number, you have to build separate TEXT commands with offsets for every label. It is a workable route, but every import is a small engineering project of its own.
A related shortcut for medium-sized lists: you can paste multiple lines of coordinates directly into the AutoCAD command line while the POINT command is running (with the command set up to repeat). It behaves like a quick, disposable script - with all the same caveats.
Method 3: Civil 3D point file import
If you have Civil 3D rather than plain AutoCAD, you have a proper survey import workflow. Civil 3D imports point files directly - typically in PNEZD format (Point number, Northing, Easting, Z elevation, Description) as a comma- or space-delimited text file - and creates intelligent Cogo points that carry their numbers, elevations, and descriptions with them.
This is the right route for genuine survey deliverables. Note the field order: PNEZD puts northing before easting, which is the opposite of AutoCAD's X,Y convention. Civil 3D handles this correctly because the format specification tells it which column is which - but it is exactly the kind of detail that goes wrong when the same file is fed into a different tool that assumes X-first ordering.
If you are on plain AutoCAD or AutoCAD LT, this method is not available - which is why so many people end up at scripts or DXF.
Method 4: DXF - usually the cleanest route
DXF (Drawing Exchange Format) is Autodesk's open interchange format, and every AutoCAD product - including LT - opens and inserts DXF files natively. The reason DXF is often the cleanest import route is simple: instead of feeding AutoCAD a list of numbers and asking it to construct geometry, a DXF already contains the geometry. Points arrive as real point entities at their correct coordinates, labels arrive as text entities, and everything can sit on its own named layers so you can toggle, restyle, or freeze it independently of the rest of the drawing.
The workflow is short: generate a DXF from your coordinate data, then in AutoCAD either open the DXF directly, or - more commonly - bring it into an existing drawing with the INSERT command (placing it at 0,0 with a scale of 1 and rotation of 0 so nothing shifts) or by copy-pasting the geometry across. Because the coordinates are baked into the file, there is no retyping, no script debugging, and no column-order guesswork.
The one thing a DXF cannot do is fix data that is in the wrong coordinate system or the wrong units - the file simply places geometry at the numbers it contains. That is why the next section matters more than the import method itself.
The gotchas: coordinate systems, units, and axis order
Almost every "my points imported in the wrong place" problem traces back to one of three causes, and none of them is the import method.
- 1. Geographic coordinates in a projected drawing. AutoCAD drawings for survey and engineering work almost always use projected coordinates - easting and northing values in metres or feet, on a grid like State Plane, UTM, or British National Grid. Raw latitude and longitude values are angles, not distances. Feed lat/long degrees into a drawing that expects metres and your entire dataset lands in a tiny cluster a few units from the origin. Lat/long must be converted to the drawing's projected system first - see Lat Long to Easting/Northing for UK work or the State Plane converter for US work.
- 2. Units that don't match the drawing. AutoCAD stores geometry in unitless drawing units - it is your project convention (and the INSUNITS setting for inserted content) that decides whether a unit is a metre, a foot, or a US Survey Foot. If the incoming coordinates are in feet and the drawing treats units as metres, everything lands roughly 3.28× too far from the origin. US State Plane data is especially prone to this because different states legislate different official units.
- 3. Swapped easting/northing order. AutoCAD is X-first: easting, then northing. Survey formats like PNEZD list northing first. A file with the columns swapped imports without any error message - the points simply appear mirrored across the drawing's diagonal, often far from the site. If your "easting" values look larger than your northings in a region where they shouldn't be, check the order before importing. See What is Easting and Northing? for the conventions.
Datum shifts are invisible until they aren't
Can't see your points? Check PDMODE
A surprisingly common post-import panic: the command line says the points were created, but the drawing looks empty. By default, AutoCAD draws point entities as single pixels - effectively invisible at most zoom levels.
Two fixes. First, run ZOOM > Extents to make sure you are actually looking at where the points landed (if they are kilometres from your title block, this also confirms a coordinate problem). Second, change the point display style: the PDMODE system variable controls how points are drawn (a value of 3 gives an X marker, for example) and PDSIZE controls how big they appear. The same settings are available through the Point Style dialog (PTYPE command).
From any coordinate format to a CAD-ready DXF
If your coordinates are not already in the projected system and units your drawing needs, the conversion and the DXF generation can happen in one step. Paste or upload your coordinates into CoordinateMapper in whatever format they arrived - lat/long, UTM, MGRS, State Plane, UK Grid, or raw eastings and northings. The parser auto-detects the format, applies the correct datum transformation, and plots everything on the map so you can visually confirm the points are where they should be before they go anywhere near your drawing.
From there, CoordinateMapper Pro exports the checked points directly as a DXF, with points and their labels placed as proper entities on their own layers - ready to open or insert into AutoCAD, Civil 3D, BricsCAD, or any other DXF-aware CAD package. It replaces the whole spreadsheet-formula-script routine with a paste, a visual check, and a download. DXF export is part of the Pro plan; CSV and KML exports and all conversions are free.
Frequently asked questions
- Q: What file format is best for importing coordinates into AutoCAD?
A: DXF, in most cases. A DXF places your points as real geometry on defined layers, works in every AutoCAD product including LT, and needs no scripting. Script files (.scr) are the traditional alternative for plain AutoCAD, and PNEZD point files are the native route in Civil 3D. - Q: Can AutoCAD import a CSV of points directly?
A: Plain AutoCAD and AutoCAD LT have no native CSV point import. The usual workarounds are building a script file from the spreadsheet, pasting coordinate lines into the command line during the POINT command, or converting the CSV to a DXF and inserting that. Civil 3D can import delimited point files (such as PNEZD) natively. - Q: Why did my points import in the wrong place?
A: The three most common causes are: lat/long degrees fed into a drawing that expects projected metres or feet (points cluster near the origin), a unit mismatch such as feet treated as metres (~3.28× displacement), and swapped easting/northing columns (points mirrored across the diagonal). A consistent offset of tens of metres usually means a datum mismatch instead. - Q: Does the coordinate system matter if I just want the points in the drawing?
A: Yes, whenever the points need to relate to anything else - existing linework, a site boundary, an OS or State Plane base map. The coordinates must be in the same projected system, datum, and units as the drawing. Only if the points are the sole content and never need to align with external data can you get away with ignoring it. - Q: How do I import survey points with their labels or point numbers?
A: In Civil 3D, import a PNEZD file and the point numbers and descriptions come in as part of each Cogo point. In plain AutoCAD, a script would need separate TEXT commands per label, which is tedious - a DXF that already contains the label text as entities alongside the points (as CoordinateMapper Pro produces) is the simpler route. - Q: My points imported but I can't see anything - are they missing?
A: Probably not. AutoCAD draws point entities as single pixels by default. Run ZOOM Extents to find them, then set PDMODE to 3 (and increase PDSIZE) or use the Point Style dialog to make them visible.
Takeaway
Getting coordinates into AutoCAD is a solved problem once you pick the right route for your situation: type them for a handful of points, script them if you enjoy spreadsheet formulas, use Civil 3D's point import for survey deliverables, or generate a DXF and let the geometry arrive ready-made. Whichever method you choose, the import succeeds or fails on the data checks, not the mechanics - confirm the coordinate system is projected and matches the drawing, confirm the units, confirm easting comes before northing, and confirm the datum. Do those four checks first and your points will land exactly where the surveyor put them. And if the same dataset is also headed for a GIS package, the equivalent workflow is covered in How to Import Coordinates into QGIS and ArcGIS.
Skip the scripts entirely
CoordinateMapper Pro converts coordinates from any format - lat/long, UTM, State Plane, UK Grid - and exports them as a CAD-ready DXF with points and labels on their own layers. Open or insert the file in AutoCAD and your points are already in place.
See what Pro includes